Errors
The Rindee API uses conventional HTTP status codes and a single, predictable error shape.
Error shape
Section titled “Error shape”Errors return JSON with a detail field describing what went wrong:
{ "detail": "Rate limit exceeded" }detail is a human-readable message. Validation errors (malformed or missing fields) may
return detail as a structured list pinpointing the offending fields.
Status codes
Section titled “Status codes”| Status | Meaning |
|---|---|
200 / 201 |
Success. |
400 |
Bad request — malformed input. |
401 |
Missing or invalid API key. See Authentication. |
403 |
Authenticated, but the key lacks the required capability. |
404 |
Resource not found. |
422 |
Validation failed — a field is missing or the wrong type. |
429 |
Rate limit exceeded. See Rate limits. |
5xx |
Server error — safe to retry idempotent requests with backoff. |
Handling errors
Section titled “Handling errors”- Branch on the HTTP status code, not on the text of
detail(messages may change). - Retry
429after theRetry-Afterheader, and5xxwith exponential backoff. - Do not retry
4xx(other than429) without changing the request.