> ## Documentation Index
> Fetch the complete documentation index at: https://developers.parkes.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Errors and rate limits

> Use HTTP status, structured error codes, and retry guidance to recover.

Handled API errors use `Content-Type: application/problem+json`. Inspect `code` for the category and `detail` for context. Preserve `request_id` when reporting a failure. Validation errors may include an `errors` object keyed by field.

Each endpoint lists the errors relevant to that operation. Unexpected server or infrastructure failures can have a different response body, so clients must handle HTTP errors even when the body is not problem JSON.

## Respond to the error

| Status | Client action |
| - | - |
| `401` | Check the credential; refresh or sign in again through your OAuth client when appropriate. |
| `403` | Check scopes and current member permissions. Repeating the same request will not expand access. |
| `404` | Check the resource ID and the organization bound to your token. |
| `409` | Inspect the error code and resolve the conflict before retrying. |
| `412` | Read the latest resource and reconcile the attempted update. |
| `422` | Correct the invalid fields using the endpoint's request schema. |
| `428` | Supply the required version precondition. |
| `429` | Wait for the number of seconds in `Retry-After`. |
| `503` | Treat the service as temporarily unavailable and retry with backoff. |

These are shared recovery conventions, not a promise that every endpoint returns every status.

## Rate limits

Request budgets are shared across credentials for a member and organization. A `429` response includes `Retry-After` in seconds. Wait before retrying and use bounded backoff to avoid repeatedly exhausting the budget.

For a mutation, preserve the same idempotency key and body when retrying the same logical operation. Do not assume a timeout means the server did not apply the change. See [writes and concurrency](https://developers.parkes.ai/WRITES.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.