ROOTEDocs
ROOTE API

ROOTE API

Use ROOTE Data and Journey capabilities over HTTP.

Page actions
https://api.roote.ai/v1

Public operations

OpenAPI is the source of truth for parameters, response schemas, and published authentication alternatives. This table summarizes the active business access rules.

MethodEndpointScopeAnonymous Free
GET/v1/geocodedata:readYes
GET/v1/place-searchdata:readYes
GET/v1/reverse-geocodedata:readYes
GET/v1/nearbydata:readYes
GET/v1/mobility/nearbydata:readYes
GET/v1/services/nearbydata:readYes
GET/v1/transit/nearbydata:readYes
GET/v1/transit/stations/{id}/departuresdata:readYes
GET, POST/v1/transit/journeyjourney:readNo
GET/v1/parking/nearbydata:readNo
GET/v1/charging/nearbydata:readNo
GET/v1/ride-hailing/estimatesdata:readNo

Parking and charging remain available in anonymous Free access only as categories of /v1/services/nearby, not through their specialized endpoints.

Current production contract

Eligible Data operations publish optional authentication in OpenAPI. Journey remains Bearer-authenticated with journey:read; invalid or revoked credentials never fall back to anonymous access.

OpenAPI

The machine-readable description is available at api.roote.ai/openapi.json. Parameter lists and schemas are not duplicated manually in this documentation.

OpenAPI describes the current contract. Release history, compatibility classification, and the publication workflow are documented separately in Changelog.

On this page