Errors
Verytis uses standard HTTP status codes and returns structured error responses with a consistent format.
Error Response Format
JSON
{
"error": {
"code": "INVALID_API_KEY",
"message": "The provided API key is invalid.",
"details": {},
"request_id": "req_..."
}
}Error Codes
| Code | HTTP Status | Description |
|---|---|---|
INVALID_REQUEST | 400 | The request body or query parameters are invalid |
INVALID_COORDINATES | 400 | The provided coordinates are out of range |
INVALID_RADIUS | 400 | The provided radius is out of range |
INVALID_API_KEY | 401 | The API key is missing, malformed, or not recognized |
API_KEY_REVOKED | 401 | The API key has been revoked |
API_KEY_EXPIRED | 401 | The API key has expired |
RESOURCE_NOT_FOUND | 404 | The requested resource does not exist |
RATE_LIMIT_EXCEEDED | 429 | Too many requests |
SOURCE_UNAVAILABLE | 503 | A required data source is temporarily unavailable |
INTERNAL_ERROR | 500 | An unexpected server error occurred |
Rate Limiting
The API enforces rate limits per API key:
- 600 requests per minute per API key
When the rate limit is exceeded, the API returns HTTP 429 with rate limit headers:
| Header | Description |
|---|---|
X-RateLimit-Limit | Maximum requests per window |
X-RateLimit-Remaining | Remaining requests in current window |
X-RateLimit-Reset | Seconds until the window resets |
Request IDs
Every API response includes a request_id in the meta object (success) or error object (failure). Include this ID when reporting issues.