Errors
Error codes returned by the API and how to handle them.
Errors use standard HTTP status codes and return a JSON body with a machine-readable code.
{
"code": "invalid_request",
"message": "identity must include at least one of email, ip or deviceId",
"docs": "https://abusezero.com/docs/errors#invalid_request"
}Error codes
| Status | Code | Meaning |
|---|---|---|
| 400 | invalid_request | The body is missing a field or has the wrong type. |
| 401 | unauthorized | The API key is missing, revoked or for another mode. |
| 404 | not_found | The check, benefit or rule doesn't exist. |
| 409 | conflict | A rule with the same name already exists. |
| 429 | rate_limited | Too many requests. Wait for Retry-After seconds. |
| 500 | internal_error | Something went wrong on our side. Safe to retry. |
Retrying safely
Send an Idempotency-Key header with every POST. If a request times out, retry with the same key and you'll get the original response instead of a duplicate check.
The official SDKs add idempotency keys and retry 429 and 5xx responses automatically.
How is this guide?
Edit on GitHub
Last updated on