Faretrotter Travel API

Name: Faretrotter Travel API API
Brand: Faretrotter Travel API
Availability: InStock

✓ Official Vendor SpecMaps GeolocationRouting DirectionsapiKey2 EndpointsREST

For Agents

Look up cities and points of interest and retrieve multimodal routes (flight, rail, bus, ferry, drive) between them.

Quickstart

Get started with Faretrotter Travel 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:
"find travel routes between cities"

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

Capabilities

What an agent can do with Faretrotter Travel API API.

Resolve cities and points of interest to canonical place identifiers usable in route queries

Retrieve multimodal route options between two places, with mode, duration, and operator details

Compare ground transport options (rail, bus, ferry) against air routes for a single origin-destination pair

Power itinerary builders that need cross-mode journey suggestions without integrating one provider per mode

GET STARTED

Start building with Faretrotter Travel API API

Explore with Jentic

View OpenAPI Document

Use for: Find all transportation options between Paris and Amsterdam, Get the train and bus routes from London to Edinburgh, Search for ferry connections between two coastal cities, List all places matching a city name for route lookup

Not supported: Does not handle fare pricing, ticketing, or reservations — use for multimodal route discovery only.

The Faretrotter Travel API returns multimodal transportation options between cities and points of interest, covering flights, trains, buses, ferries, and driving routes. Agents can query the places catalogue to resolve city and POI identifiers, then pull the available routes between any two locations. The service is designed for travel planners, itinerary builders, and aggregators that need a single source for cross-mode journey options.

Use Cases

Patterns agents use Faretrotter Travel API API for, with concrete tasks.

★ Multimodal Itinerary Builder

Travel planning apps use Faretrotter to populate trip segments with all viable transport options between two cities. The /routes endpoint returns flights, trains, buses, ferries, and drive routes in a single call, so the planner does not need to integrate Skyscanner, Trainline, and bus aggregators separately. Integration takes a few hours given the spec only exposes two endpoints.

Resolve 'Paris' and 'Berlin' via /places, then call /routes to return the full list of transport options between them with mode and duration

Ground-Transport Fallback for Flight Search

Flight aggregators use Faretrotter to suggest rail or bus alternatives when a route has no available flights or fares exceed a threshold. The agent calls /routes for the same origin and destination and filters returned options by mode to surface ground alternatives. Adds resilience to itinerary search without a separate rail or bus integration.

When a flight search returns zero results between two cities, call /routes to fetch ground options and present rail and bus alternatives ranked by duration

Points of Interest Reachability

Travel guides and destination marketing sites use Faretrotter to show how reachable a point of interest is from major hub cities. The /places endpoint resolves the POI to an identifier, then /routes returns the modes and times from each candidate origin. Useful for SEO landing pages that answer 'how do I get to X from Y'.

Look up the Eiffel Tower in /places, then call /routes from a list of European hub cities and produce a reachability table

AI Travel Concierge via Jentic

Conversational travel agents use Jentic to call Faretrotter without managing API keys directly. The agent resolves a user's free-text origin and destination through /places, then queries /routes to return options that fit the user's constraints. Jentic isolates the apikey path-segment credential so the agent never sees the raw key, and the search-load-execute flow takes minutes instead of days.

Through Jentic, search 'find travel routes between cities', load the /routes operation, and return options for a user's requested origin-destination pair

Key Endpoints

2 endpoints — the faretrotter travel api returns multimodal transportation options between cities and points of interest, covering flights, trains, buses, ferries, and driving routes.

METHOD

PATH

DESCRIPTION

GET

/places

List or look up cities and points of interest

GET

/routes

Retrieve multimodal routes between two places

GET

/places

List or look up cities and points of interest

GET

/routes

Retrieve multimodal routes between two places

Why though Jentic?

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

Credential isolation

The Faretrotter apikey path segment is stored encrypted in the Jentic vault. Agents call the operation by intent and Jentic injects the credential into the URL at execution time — the raw key never enters the agent's context.

Intent-based discovery

Agents search 'find travel routes between cities' and Jentic returns the /routes operation with its place-id input schema, so the agent calls the right endpoint without browsing Faretrotter docs.

Time to first call

Direct integration: half a day for path-segment auth, place lookup, and route parsing. Through Jentic: under 30 minutes — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Amadeus Flight Offers Price

Pull live flight fares once Faretrotter has identified that flying is a viable mode

Choose Amadeus when the user wants priced flight options; use Faretrotter first to confirm flight is even an option for the route

Complementary

Booking.com

Add accommodation booking to itineraries built from Faretrotter routes

Choose Booking.com when the user has selected a destination and needs lodging; Faretrotter handles the get-there leg

Alternative

Transit

Public transit-focused alternative for intra-city travel

Choose Transit for urban public transport routing; choose Faretrotter for inter-city multimodal options

FAQs

Specific to using Faretrotter Travel API API through Jentic.

What authentication does the Faretrotter Travel API use?

Faretrotter uses an API key passed as a path segment in the base URL (https://api.faretrotter.com/v2.0/{apikey}). Through Jentic the key is stored encrypted in the vault and injected into the URL at execution time, so the key never enters the agent's prompt context.

Can I get multimodal routes with the Faretrotter Travel API?

Yes. The /routes endpoint returns flight, rail, bus, ferry, and drive options between two places in a single response. Resolve the origin and destination through /places first to get the identifiers /routes expects.

What are the rate limits for the Faretrotter Travel API?

Faretrotter does not publish explicit rate limits in the OpenAPI spec. Treat it as a metered travel data service, cache /places lookups since identifiers are stable, and back off on 429 responses if you hit them.

How do I look up routes between two cities through Jentic?

Install the SDK with pip install jentic, search for 'find travel routes between cities', load the /routes operation, and execute with the resolved origin and destination identifiers from /places. Sign up at https://app.jentic.com/sign-up.

Does the Faretrotter Travel API include pricing or booking?

No. The spec exposes /places and /routes only — there is no fare quote or booking endpoint. Use Faretrotter for option discovery, then hand off to a booking provider such as Amadeus or Skyscanner for fares and reservations.