Delete plan (Usage-Based only)
Overview
Deletes a partner-managed usage-based plan and removes its plans link to the partner.
Prerequisites
- A bearer token. Callable with Partner tokens.
- The
planIdof the record you are targeting.
Base URL
| Environment | URL |
|---|---|
| Production | https://production-api.shoutaboutus.com |
| Development | https://development-api.shoutaboutus.com |
Endpoint
DELETE /api/v1/partner/plans/{planId}
Authentication
- Requires a bearer token in the
Authorization: Bearer <bearer-token>header. - Who can call it: Partner tokens.
Validation rules:
- Usage-based, partner-managed plans only.
- Returns 403 in any of these cases. No authenticated partner is found, the plan is not usage-based or is admin-managed, the plan is not linked to the partner, or the caller is a sub-partner.
- Returns 422 if the plan ID is invalid or doesn't exist.
Rate limit
- No rate limit.
Path parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
planId | integer | Required | Digits only. |
Path parameters
| Param | In | Type | Required | Description |
|---|---|---|---|---|
planId | path | integer | Yes | Plan ID (route [0-9]+); must be an existing plan belonging to the partner. |
Response
200 OK · 200
200{ "data": { "message": "Plan deleted." } }Errors
| Status | Meaning |
|---|---|
401 | The bearer token is missing, expired, or invalid |
403 | The caller lacks permission (not authenticated, is a sub-partner, plan is not usage-based or is admin-managed, or plan is not linked to the partner) |
422 | The request failed validation — the response names the fields (includes invalid or non-existent plan IDs) |
500 | Unexpected server error |
Example request
curl --request DELETE \
--url "https://production-api.shoutaboutus.com/api/v1/partner/plans/123" \
--header 'Authorization: Bearer <bearer-token>' \
--header 'Accept: application/json'Updated 10 days ago
Did this page help you?
