canonical: https://jentic.com/apis/transitapp.com/transitapp

# Transitapp Transit API

API provided by data from transit.app. The API exposes 16 endpoints secured with apiKey authentication.

## For AI agents

Programmatically get transit routes which are near a location, get transit stops which are near a location. Covers 16 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for maps and geolocation only.

## Capabilities

- Get transit routes which are near a location
- Plan a trip from origin to destination (OTP)
- Estimate a trip plan duration (Preview)
- Query and filter Transit API records by parameters
- Monitor Transit API operational status and events

## Use cases

### Maps and Geolocation Operations

Use the Transit API to perform maps geolocation operations programmatically. The API provides 16 endpoints covering core functionality including get transit routes which are near a location, get transit stops which are near a location, get upcoming departures for all routes serving a stop.

Example prompt: Call GET /public/nearby_routes to get transit routes which are near a location

### Automated Public transport Management

Automate public transport operations by combining multiple Transit API endpoints. Agents can get transit stops which are near a location and then get upcoming departures for all routes serving a stop in a single workflow.

Example prompt: Call GET /public/nearby_stops to get transit stops which are near a location, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Transit API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Example prompt: Search Jentic for 'get transit routes which are near a location', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /public/nearby_routes | Get transit routes which are near a location |
| GET | /public/nearby_stops | Get transit stops which are near a location |
| GET | /public/stop_departures | Get upcoming departures for all routes serving a stop |
| GET | /otp/plan | Plan a trip from origin to destination (OTP) |
| GET | /public/estimate_plan_duration | Estimate a trip plan duration (Preview) |
| GET | /public/plan | Plan a trip (Preview) |
| GET | /map_layers/placemarks | Get a list of placemarks |
| GET | /public/available_networks | Get a list of available networks |

## Key resources

- **Public transport** — Operations related to Public transport
- **Shared mobility** — Operations related to Shared mobility

## Why Jentic

- **Setup:** Wiring the Transit API by hand means setting up its apiKey header auth against external.transitapp.com and handling error responses yourself. Through Jentic you install once, import the Transit API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** The Transit API is read-only, with locations passed as query parameters rather than owned resource ids in the URL path, so scope the agent to the operations it needs, such as nearby routes, nearby stops, or stop departures, and leave out anything the workflow does not require. Every operation you allow is one you have chosen.
- **Credential handling:** Your Transit API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'get transit routes near a location' or 'get upcoming stop departures', and Jentic returns the matching Transit API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Here** — Alternative maps geolocation API
- **Tomtom** — Alternative maps geolocation API
- **Googleapis** — Complementary maps geolocation API

## FAQ

### What authentication does the Transit API use?

The Transit API uses an API key passed in the `apiKey` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I get transit routes which are near a location with the Transit API?

Yes. Use the GET /public/nearby_routes endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Transit API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I get transit routes which are near a location through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get transit routes which are near a location'. Jentic returns the matching Transit API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Transit API have?

The Transit API exposes 16 endpoints covering public transport, shared mobility operations.

### Can I limit what my agent is allowed to do with the Transit API?

Yes. Because Jentic One is self-hosted, you decide which Transit API operations your agent may call, so you can allow just the ones a workflow needs, such as GET /public/nearby_routes, GET /public/nearby_stops, or GET /public/stop_departures, and leave out trip planning or placemark lookups. The Transit API is read-only and takes locations as query parameters, so an allowed agent can fetch nearby routes and departures but cannot create or change anything. Your API key is held encrypted by your own instance and injected at call time, so the agent only ever exercises the operations you have permitted.