ROOTEDocs
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

HTTPCodeMeaning
401INVALID_API_TOKENBearer is malformed or unknown
401REVOKED_API_TOKENKey is revoked or its project is inactive
401API_TOKEN_REQUIREDThe capability does not permit anonymous access
402INSUFFICIENT_CREDITSThe project cannot reserve the required credits
403SCOPE_NOT_ALLOWEDThe key lacks data:read or journey:read
403INTERNAL_ACCESS_REQUIREDThe capability requires an internal project
403CAPABILITY_FORBIDDENAccess is disabled by capability policy
429RATE_LIMITEDRequest frequency limit reached; respect Retry-After
503AUTH_UNAVAILABLEAuthentication 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.

On this page