canonical: https://jentic.com/apis/duffel.com/duffel # Duffel API The Duffel API searches for flights and books them on behalf of travelers. You can create an offer request to search availability, read the returned offers, place and manage orders, and look up reference data such as airports, airlines, aircraft, and seat maps. It covers the flight search-and-book flow end to end. ## For AI agents Search for flights by creating offer requests, read and compare offers, book and manage orders, and look up airport, airline, aircraft, and seat-map reference data through the Duffel API. ## Scope Covers flight search and booking plus related reference data. Does not handle hotels, car rental, or payment processing outside the flight order flow. ## Capabilities - Create an offer request to search flight availability - Read and compare the offers returned for a search - Place an order to book a selected offer - Retrieve and update existing orders - Look up airports, airlines, and aircraft reference data - Fetch seat maps for an offer ## Use cases ### AI Agent Flight Search An AI agent can search flight availability by creating an offer request and reading the offers that come back. Through Jentic the agent finds the search operation by intent and supplies origin, destination, and dates, so a travel assistant can present flight options to a user without a developer wiring the endpoints by hand. Example prompt: Create an offer request for a route and date, then return the cheapest offers with their prices ### Automated Flight Booking A travel workflow agent can complete a booking by placing an order for a chosen offer and then reading the order back to confirm it. The API creates and retrieves orders, so an agent can book a selected flight for a passenger and report the confirmation, with human approval gated by scoping rules. Example prompt: Place an order for a selected offer with passenger details and return the order confirmation ### Travel Reference Lookup An agent can resolve travel reference data such as airports, airlines, aircraft, and seat maps to enrich its answers. The API exposes these lookups, so an assistant can translate a city into an airport code or show a seat map for a chosen offer alongside the booking flow. Example prompt: Look up the airports for a city and return their codes and names ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | `/air/offer_requests` | Create an offer request to search flights | | GET | `/air/offers` | List offers for a request | | GET | `/air/offers/{id}` | Get a single offer | | POST | `/air/orders` | Place an order to book an offer | | GET | `/air/orders` | List orders | | GET | `/air/orders/{id}` | Get an order by id | | GET | `/air/airports` | List airports | | GET | `/air/airlines` | List airlines | ## Key resources - **Offer Requests** — Create a search for flight availability across routes and dates - **Offers** — Read and compare the flight offers returned for a request - **Orders** — Place, retrieve, and update flight bookings - **Reference Data** — Look up airports, airlines, aircraft, and seat maps ## Why Jentic - **Setup:** Wiring Duffel by hand means managing an access token, sending it as a bearer token on every request, and mapping the search-and-book operations. Through Jentic you install once, import Duffel from the API Directory, store the token once, and your agent calls it. - **Permission scoping:** You decide which Duffel operations the agent may use. Allow it to search offers while blocking order creation, and because order and offer ids sit in the URL path, a rule can restrict it to specific bookings so it cannot place or change orders you did not approve. - **Credential handling:** Your Duffel access token is stored encrypted by your own Jentic One instance and injected as a bearer token at execution time. It never enters the agent's prompt, logs, or context window. - **Discovery method:** Agents search Jentic by intent such as 'search flight offers' or 'create a flight order', and Jentic returns the matching Duffel operation with its input schema so the agent calls the right endpoint. ## Related APIs - **Amadeus Flight Offers Price** — Amadeus prices flight offers as part of its travel platform. - **Amadeus Flight Create Orders** — Amadeus creates flight orders through its booking API. - **Amadeus for Developers** — Amadeus offers broad travel APIs including hotels, transfers, and trip data. ## FAQ ### Is there a Duffel MCP server? You don't need an MCP server to give your agent the Duffel API. Jentic connects it directly from the API Directory: import it, store your token once, and your agent can search offers and book flights. Operations are discovered on demand, so no extra tool definitions sit in the agent's context. ### Can I restrict what my agent is allowed to do with the Duffel API? Yes. You choose which operations the agent may call, so you can allow it to search offers but not place orders, keeping booking under human control. Because order and offer ids appear in the URL path, a rule can also pin the agent to specific orders, and every call is logged. ### What authentication does the Duffel API use? The Duffel API authenticates with a bearer token, sent in the Authorization header per its OpenAPI spec. Through Jentic the token is stored encrypted by your own Jentic One instance and added to each request at call time, so it never appears in the agent's prompt or logs. ### Can my agent book a flight with the Duffel API? Yes. After searching offers, the agent can place an order for a selected offer with passenger details and then retrieve the order to confirm it. You can keep booking gated behind a scoping rule so the agent only searches until a person approves the order. ### What are the rate limits for the Duffel API? The OpenAPI spec does not specify rate limits. Check the Duffel documentation at https://duffel.com/docs for the current request limits and offer expiry rules before running high-volume searches. ### How do I search for flights through Jentic? Search Jentic for 'search flight offers with Duffel', import the operation, and store your access token once. Your agent then creates offer requests and reads offers on demand. To run it on your own infrastructure, install Jentic One from its GitHub repo.