ROOTE API
Use ROOTE Data and Journey capabilities over HTTP.
Page actions
https://api.roote.ai/v1Public operations
OpenAPI is the source of truth for parameters, response schemas, and published authentication alternatives. This table summarizes the active business access rules.
| Method | Endpoint | Scope | Anonymous Free |
|---|---|---|---|
| GET | /v1/geocode | data:read | Yes |
| GET | /v1/place-search | data:read | Yes |
| GET | /v1/reverse-geocode | data:read | Yes |
| GET | /v1/nearby | data:read | Yes |
| GET | /v1/mobility/nearby | data:read | Yes |
| GET | /v1/services/nearby | data:read | Yes |
| GET | /v1/transit/nearby | data:read | Yes |
| GET | /v1/transit/stations/{id}/departures | data:read | Yes |
| GET, POST | /v1/transit/journey | journey:read | No |
| GET | /v1/parking/nearby | data:read | No |
| GET | /v1/charging/nearby | data:read | No |
| GET | /v1/ride-hailing/estimates | data:read | No |
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.