Error response format
Most error responses return a JSON body with anerror field:
Content-Type response header when parsing errors programmatically.
HTTP status codes
| Status | Meaning |
|---|---|
200 OK | Request succeeded. |
400 Bad Request | Invalid parameters or missing required fields. |
401 Unauthorized | Missing, invalid, or insufficient API key. |
403 Forbidden | Your plan does not include this feature. |
404 Not Found | Resource does not exist or does not belong to your account. |
429 Too Many Requests | Rate limit exceeded (100 requests per 2-minute window). |
500 Internal Server Error | Unexpected server error. |
Common errors
401 — Missing API key
401 — Missing API key
The Add the header to your request:
Authorization header is absent or does not start with Bearer .401 — Invalid API key
401 — Invalid API key
The key in the Verify that the key is copied correctly and has not been deleted. You can manage your keys in Settings > API Keys.
Authorization header does not match any active key on your account.401 — Invalid permissions
401 — Invalid permissions
The key has Either switch to a
read_only permission but the request uses a write method (POST, PUT, or DELETE).GET request or use an all_access key.403 — Plan does not include API access
403 — Plan does not include API access
The account associated with the API key is not on a Starter or Growth plan.Upgrade your plan to enable API access.
404 — Resource not found
404 — Resource not found
The requested resource does not exist, or it belongs to a different account.Confirm the ID is correct and that the resource was created under the same account as your API key.
429 — Rate limit exceeded
429 — Rate limit exceeded
You have sent more than 100 requests in a 2-minute window from the same IP address.Wait before retrying. Implement exponential backoff to avoid hitting the limit repeatedly.
