ROOTE API
Errors
ROOTE API access and request error reference.
Page actions
ROOTE returns structured errors:
{ "error": { "code": "RATE_LIMITED", "message": "Request rate limit exceeded." } }Access and platform errors
| HTTP | Code | Meaning |
|---|---|---|
| 401 | INVALID_API_TOKEN | Bearer is malformed or unknown |
| 401 | REVOKED_API_TOKEN | Key is revoked or its project is inactive |
| 401 | API_TOKEN_REQUIRED | The capability does not permit anonymous access |
| 402 | INSUFFICIENT_CREDITS | The project cannot reserve the required credits |
| 403 | SCOPE_NOT_ALLOWED | The key lacks data:read or journey:read |
| 403 | INTERNAL_ACCESS_REQUIRED | The capability requires an internal project |
| 403 | CAPABILITY_FORBIDDEN | Access is disabled by capability policy |
| 429 | RATE_LIMITED | Request frequency limit reached; respect Retry-After |
| 503 | AUTH_UNAVAILABLE | Authentication or PostgreSQL is unavailable |
Validation and result states
Other documented request errors include missing_query and invalid_coordinates. An empty result is not always an error: geography may return results: [], and Nearby responses distinguish successful, empty, partial, and unavailable coverage. Preserve the response status and freshness metadata rather than converting every empty or partial result into an error.