api reference · v1
Errors
Updated May 12, 2026
Every Siftfy API response uses standard HTTP status codes. Failures come with a JSON body containing a message and a request_id you can include in support tickets.
Status codes
| status | when | retry? |
|---|---|---|
| 401 | Missing or invalid X-API-Key. See authentication. | No — fix the key. |
| 413 | Request body larger than 25 KB. | No — trim the input. |
| 422 | Body fails validation (e.g. empty text, wrong type, malformed JSON). | No — fix the request shape. See /v1/predict. |
| 429 | Per-minute or daily quota exceeded. Response carries Retry-After. | Yes — back off and retry. See rate limits. |
| 503 | Inference service temporarily unavailable. | Yes — exponential backoff with jitter. |
Response body
Errors return a JSON object with a human-readable message and a request_id. Both are safe to log; neither contains the request body.
Where to next
- Rate limits → the X-RateLimit-* headers and how to ramp inside the cap.
- SDKs → the Python client maps each status to a typed exception and handles retries.
- Contact → include a
request_idand we can pull it from the logs.