ROOTE API
View StatusGet API key

ROOTE API · CHECKING

The urban data layer your product can trust.

Access shared mobility, public transport, geocoding and essential city services through one normalized API. Freshness, provenance and incomplete coverage stay explicit.

Get Key Read Documentation
ROOTE MCP Explore OpenAPI
BASE URLhttps://api.roote.ai/v1
4data domains
13public operations
1normalized contract
2.0.0live API version

ONE URBAN DATA LAYER

From coordinates to useful context.

Use specialized endpoints when you need depth, or request several families through the global nearby endpoint.

01

GLOBAL

Nearby aggregation

Mobility, public transport and urban services in one request, with family-level status and diagnostics.

GET /v1/nearby
02

MOBILITY

Shared vehicles & stations

Bicycles, scooters, mopeds, cars, stations, availability, battery and operator actions.

GET /v1/mobility/nearby
03

TRANSIT

Stops, departures & journeys

Nearby stops, scheduled and real-time departures, cancellations and multimodal journey planning.

GET /v1/transit/nearby
04

SERVICES

City essentials

Parking, EV charging, toilets, AEDs, Wi-Fi, fountains and lockers around any coordinate.

GET /v1/services/nearby
05

PLACES

Geocoding & search

Resolve addresses, POIs and coordinates into ranked geographic candidates.

GET /v1/geocode

NORMALIZED BY DESIGN

Provider complexity stays behind the API.

ROOTE calls the relevant sources, normalizes their models, resolves identities and preserves what applications need to judge reliability.

  • ✓ Canonical entities and stable ROOTE IDs
  • ✓ Field-level provenance and freshness
  • ✓ Cache and single-flight protection
  • ✓ Explicit partial coverage and provider errors
  • ✓ Silent server-side limits with transparent metadata
  1. 01
    Your applicationOne authenticated request
  2. 02
    ROOTE orchestrationCache · budgets · fallback
  3. 03
    Urban providersMobility · transit · services
  4. 04
    Canonical responseNormalized · deduplicated · traceable

PUBLIC API

The active endpoint catalog.

Discover

  • GET/v1/nearbyGlobal nearby
  • GET/v1/mobility/nearbyShared mobility
  • GET/v1/services/nearbyUrban services

Transit

  • GET/v1/transit/nearbyStops and stations
  • GET/v1/transit/stations/{id}/departuresUpcoming departures
  • GET/v1/transit/journeyA → B journeys

Places

  • GET/v1/geocodeAddress to coordinates
  • GET/v1/place-searchPOI search
  • GET/v1/reverse-geocodeCoordinates to place

Platform

  • POST/v1/capabilitiesContract 1.0.0
  • GET/openapi.jsonOpenAPI 3.1
  • GET/healthLive health

START IN MINUTES

One key. One request.

Create a developer project, issue a token with the data:read scope and send it as a Bearer credential.

  1. 1
    Create a project

    Use the ROOTE developer portal.

  2. 2
    Generate an API key

    Keep it server-side and out of source control.

  3. 3
    Call the API

    Inspect status, freshness and coverage.

cURL
curl --request GET \
  --url 'https://api.roote.ai/v1/nearby?lat=44.8378&lon=-0.5792&families=mobility,transit,services' \
  --header 'Authorization: Bearer $ROOTE_API_TOKEN'
Scope required: data:read

BUILT FOR PRODUCTS

One layer, many experiences.

01

Mobility maps

Display live shared vehicles, stations, services and transit with a unified model.

02

Travel assistants

Give users location-aware answers grounded in structured urban data.

03

Intermodal routing

Combine nearby discovery, departures and public transport journeys.

04

City applications

Surface practical infrastructure from chargers to AEDs and accessible transport.

BUILD WITH ROOTE

Connect your product
to the city.

Start with the OpenAPI contract or create a developer key.

Get your API key Read the documentation Check API health
Copied