The HTTP status codes Shape returns, what each one means, and how to handle errors.
Shape uses standard HTTP status codes. A 2xx means the request succeeded; a 4xx means something in the request needs to change. On any error, read the response body for a code and message that explain what went wrong.
Reference
| Code | Meaning |
|---|---|
| 200 OK | The request was received, understood, and processed. |
| 400 Bad Request | A required field or parameter is missing, a value is invalid, or the combination of fields isn’t valid. Check your request body and parameters. |
| 401 Unauthorized | Missing or invalid credentials — usually an absent or incorrect API Authorization Key. |
| 404 Not Found | The resource doesn’t exist — for example, a record ID that isn’t in your account. |
| 409 Conflict | The request conflicts with an existing resource — for example, creating a calendar event at a time that’s already taken. |
| 429 Too Many Requests | You’ve exceeded your rate limit. Back off and retry — see Rate Limits. |
Error response body
Errors return a machine-readable code alongside a human-readable message:
{
"status": 400,
"error": "Bad Request",
"message": "A required field or parameter is missing or invalid."
}Branch on the HTTP status code first, then surface
message for debugging. Don’t parse success or failure out of the message text — it’s meant for humans and can change between releases.