Navitia API

Name: Navitia API API
Brand: Navitia API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMaps GeolocationRouting Directionsbasic9 EndpointsREST

For Agents

Plan multimodal journeys, get departures and arrivals, build isochrones, and look up transit lines and disruptions across Navitia coverage regions.

Quickstart

Get started with Navitia API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"plan a public transit journey between two coordinates"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Navitia API API.

Plan a multimodal journey between two points across a Navitia coverage region

Compute an isochrone polygon showing reachable area within a travel-time budget

List the transit lines, stop areas, and places served inside a coverage region

Retrieve real-time departures and arrivals for a stop area on the chosen network

GET STARTED

Start building with Navitia API API

Explore with Jentic

View OpenAPI Document

Use for: Plan a public transit journey from Gare du Nord to Charles de Gaulle Airport, Get the next departures from a stop area in Paris, Compute an isochrone showing where I can reach within 30 minutes by transit, List all transit lines on the Île-de-France Navitia coverage

Not supported: Does not handle ride-hailing dispatch, vehicle telemetry, or driving turn-by-turn navigation — use for public transit journey planning, isochrones, departures, and disruptions only.

Jentic publishes the only available OpenAPI document for Navitia API, keeping it validated and agent-ready.

Navitia is an open multimodal transit API built on top of GTFS and other open transport datasets. It exposes coverage regions, journey planning, isochrones, transit lines, stop areas, real-time departures and arrivals, places search, and disruption feeds for the cities and regions it covers. Authentication uses HTTP Basic with the API key as the username, and responses follow the Navitia v1 hypermedia model.

Use Cases

Patterns agents use Navitia API API for, with concrete tasks.

★ Multimodal Journey Planning

Trip-planning apps need a multimodal journey engine that combines walking, public transit, and bike legs across a city. Navitia's /coverage/{region}/journeys endpoint accepts origin and destination coordinates and returns ranked itineraries with leg-level transit information sourced from GTFS feeds. The result is suitable for direct rendering in a journey planner UI.

Call /coverage/fr-idf/journeys with from and to coordinates to return the top 3 ranked itineraries between Gare du Nord and Charles de Gaulle Airport.

Isochrones for Reach Analysis

Property platforms, employer dashboards, and urban-planning tools use isochrones to show areas reachable from a point within a travel-time budget. The /coverage/{region}/isochrones endpoint returns the polygon describing reachable area from the input coordinates, given a maximum duration. Visualising the polygon on top of a map produces a transit accessibility layer in minutes.

Call /coverage/fr-idf/isochrones with the user's home coordinates and max_duration=1800 seconds to return the 30-minute transit reach polygon.

Real-Time Departures and Disruptions

Mobility products need to surface real-time departures and any disruptions affecting a journey. Navitia's /coverage/{region}/stop_areas/{stopAreaId}/departures returns the next scheduled and real-time departures from a stop, while /coverage/{region}/disruptions exposes the current incident feed. Combined, they let an app display 'next train' alongside any service alerts.

For a chosen stop area, call /coverage/fr-idf/stop_areas/{stopAreaId}/departures and /coverage/fr-idf/disruptions, then return the next departures with any active disruptions annotated.

Agent-Driven Transit Assistance via Jentic

Travel and concierge agents need to plan transit journeys for a user without integrating Navitia auth and pagination by hand. Through Jentic the agent searches by intent, loads the schema for the journey or departures operation, and executes it with origin and destination, while Jentic stores the basic auth credentials in its vault. The agent receives a structured itinerary it can summarise to the user.

Search Jentic for 'plan a public transit journey between two coordinates', load the schema for /coverage/{region}/journeys, and execute it with the user's origin and destination.

Key Endpoints

9 endpoints — navitia is an open multimodal transit api built on top of gtfs and other open transport datasets.

METHOD

PATH

DESCRIPTION

GET

/coverage

List Navitia coverage regions

GET

/coverage/{region}/journeys

Plan a multimodal journey on a coverage region

GET

/coverage/{region}/isochrones

Compute an isochrone polygon for a coverage region

GET

/coverage/{region}/stop_areas

List stop areas on a coverage region

GET

/coverage/{region}/lines

List transit lines on a coverage region

GET

/coverage/{region}/stop_areas/{stopAreaId}/departures

Get next departures from a stop area

GET

/coverage/{region}/disruptions

List current disruptions on a coverage region

GET

/coverage/{region}/places

Search places on a coverage region

GET

/coverage

List Navitia coverage regions

GET

/coverage/{region}/journeys

Plan a multimodal journey on a coverage region

GET

/coverage/{region}/isochrones

Compute an isochrone polygon for a coverage region

GET

/coverage/{region}/stop_areas

List stop areas on a coverage region

GET

/coverage/{region}/lines

List transit lines on a coverage region

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The Navitia API key is stored encrypted in the Jentic vault and applied as HTTP Basic auth (key as username, empty password) at execution time. Agents call Navitia operations through Jentic without seeing the raw key.

Intent-based discovery

Agents search Jentic by intent (e.g. 'plan a public transit journey between two coordinates') and Jentic returns the matching Navitia operation with its input schema for direct execution.

Time to first call

Direct integration with Navitia: 2-3 days to handle the hypermedia response model, region selection, and basic auth wiring. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

TomTom Search API

Place search and geocoding that pairs with Navitia journey planning for richer trip UIs.

Use TomTom Search when the agent needs to resolve a place query before passing coordinates into a Navitia journey call.

Alternative

HERE Maps API

Commercial routing and transit API offering global coverage and driving directions.

Pick HERE when the workflow needs door-to-door driving routes or coverage outside Navitia's regions.

Complementary

OpenCage Geocoding API

Geocodes addresses to coordinates that feed into Navitia journey and isochrone calls.

Call OpenCage first when the agent only has a postal address and needs lat/lon for the Navitia request.

FAQs

Specific to using Navitia API API through Jentic.

What authentication does the Navitia API use?

Navitia uses HTTP Basic authentication where the API key is sent as the basic-auth username with an empty password. Jentic stores the key in its vault and supplies the basic auth header on each request so the agent never sees the raw key.

Can I plan a journey between two coordinates with the Navitia API?

Yes. GET /coverage/{region}/journeys with from and to query parameters expressed as lat;lon (or place IDs) returns ranked multimodal itineraries with leg-level public transport detail.

What are the rate limits for the Navitia API?

Navitia's free tier limits requests per second per token and applies daily caps; commercial plans raise the limits. The OpenAPI spec does not publish exact quotas — review your plan at navitia.io/en/pricing before running batch isochrones or large journey loops.

How do I plan a transit journey through Jentic?

Run pip install jentic, search for 'plan a public transit journey between two coordinates', load the schema for /coverage/{region}/journeys, and execute it with the desired region and from/to parameters. Sign up at https://app.jentic.com/sign-up.

Does Navitia cover the United States?

Coverage depends on which GTFS and real-time feeds Navitia ingests for a region. Call /coverage to enumerate the active coverage regions on your account; not all US cities are available, and some regions are read-only or limited to schedules without real-time data.

Does this API include driving directions?

Navitia is focused on multimodal public transport including walking and bike legs. Pure car routing is not Navitia's primary scope; for door-to-door driving directions use a routing engine such as TomTom or HERE.