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. These are the outcomes an integration should handle deliberately.
Success codes
| Code | Meaning | When you'll see it |
|---|---|---|
200 OK | Success | Successful GET, PATCH, PUT, DELETE, and dedicated mutation responses |
201 Created | Resource created | Successful POST that created a new record |
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 | An API key was sent to an unsupported native /api/ route | Use the versioned /partners/ path instead |
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 | A draft block or theme-setting mutation used a stale ifUpdatedAt value | Refetch the draft, reconcile changes, and retry |
422 Unprocessable Entity | A dedicated mutation contains an unknown block, field, setting, or guarded field | Read the validation issues, fetch the matching schema endpoint, 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 an idempotent read once; verify a write's outcome before retrying it, and contact support with the request ID if the failure persists |
Error envelope
Partner routes return JSON errors with an error and message; validation responses may also include errors, and most route-level failures include a requestId. See Errors.
Related
- Authentication: common cause of 401 responses.
- Errors: full error envelope.
- Rate limits: handling 429 responses.