Status codes
HTTP status codes returned by the Basker Partners API, with the meaning each one carries
The Basker Partners API uses standard HTTP status codes. The list below covers every code you should expect to see, what it means, and what to do about it.
Success codes
| Code | Meaning | When you'll see it |
|---|---|---|
200 OK | Success | Most successful GET, PATCH, PUT, DELETE responses |
201 Created | Resource created | Successful POST that created a new record |
204 No Content | Success, no body | Some successful operations that don't return data |
Client error codes
| Code | Meaning | What to do |
|---|---|---|
400 Bad Request | The request was malformed or missing required parameters | Check the response body for which field is invalid; fix and retry |
401 Unauthorized | Missing or invalid Authorization header | Confirm the API key is correct and the header is formatted as expected — see Authentication |
403 Forbidden | Authentication succeeded, but the API key isn't allowed to perform this action on this tenant | Confirm the tenant slug and the API key's permissions; the most common cause is using a non-Partners-API key path |
404 Not Found | No record matches the request, or the path doesn't exist | Confirm the endpoint path, version, tenant slug, and record ID |
409 Conflict | The request conflicts with current state (e.g. duplicate slug) | Check the response body; resolve the conflict and retry |
422 Unprocessable Entity | Request body is structurally valid but fails validation rules | Read the validation errors in the response body; fix and retry |
429 Too Many Requests | Rate limit exceeded — see Rate limits | Wait for the duration in Retry-After, then retry |
Server error codes
| Code | Meaning | What to do |
|---|---|---|
500 Internal Server Error | Unexpected server-side failure | Retry once; if it persists, contact support with the request ID from the response |
502 Bad Gateway | Upstream service unavailable | Retry with exponential backoff |
503 Service Unavailable | Platform temporarily unavailable (deployment, maintenance) | Retry after a short delay |
504 Gateway Timeout | Upstream took too long to respond | Retry; if persistent on a specific request, simplify the request (smaller pages, fewer fields) |
Error envelope
Every non-2xx response carries a JSON body in a consistent shape. See Errors for the envelope structure and how to parse it.
Related
- Authentication — common cause of 401 responses.
- Errors — full error envelope.
- Rate limits — handling 429 responses.