Status and Error Codes
Live
Reference endpoint — the status values a data API can return and the typed error codes a request can fail with.
Environment
| Environment | Base URL |
|---|---|
| Production | https://api.sadafiles.com/v1 |
There is one environment and no sandbox, so every request here is real and counts toward your limits.
Request
GEThttps://api.sadafiles.com/v1/apis/status-and-error-codes
- Provider
- Reference
- Category
- Reference
- Auth
- X-API-Key with tools:run
- Rate weight
- 2 units
- Daily allowance
- 1,000 calls per account, shared across data APIs
- Response type
- JSON
Response
200 OK
{
"slug": "status-and-error-codes",
"status": "success",
"statuses": [
"success",
"planned"
],
"errors": [
{
"code": "not_implemented",
"http": 501,
"meaning": "Endpoint is on the roadmap but not yet live."
},
{
"code": "INVALID_INPUT",
"http": 400,
"meaning": "A required parameter is missing or malformed."
},
{
"code": "UNAUTHENTICATED",
"http": 401,
"meaning": "Missing or invalid developer API key."
},
{
"code": "FORBIDDEN",
"http": 403,
"meaning": "API key lacks the required scope, or account suspended."
},
{
"code": "RATE_LIMITED",
"http": 429,
"meaning": "Per-key daily quota or fair-use budget exhausted."
},
{
"code": "SERVICE_UNAVAILABLE",
"http": 503,
"meaning": "The upstream provider blocked or rate-limited the request."
},
{
"code": "TIMEOUT",
"http": 504,
"meaning": "The upstream provider did not respond in time."
}
]
}Try it yourself!
Change a value and the code updates. Run sends the real request with your key and counts toward your limits.