Amadeus Flight Create Orders
Browse all Amadeus APIs0
AI ReadinessNon-Ready (F)0/100
Official vendor OpenAPI document · agent-readyE CommerceOrder Managementoauth21 EndpointsREST
For Agents
Create a confirmed flight booking from a priced Amadeus flight offer, returning the order id and PNR reference an agent can use for downstream ticketing or order management.
Use for: Book the flight offer the user just confirmed, Create an Amadeus flight order for two adult travellers, I want to issue a PNR for this priced flight offer, Submit traveller passport details and create a flight booking
Not supported: Does not search for flights, reconfirm prices, capture payment, or modify existing orders - use only to create a new flight order from an already-priced offer.
The Amadeus Flight Create Orders API turns a priced flight offer into a confirmed booking with a Passenger Name Record. The single POST endpoint takes a flight offer (already validated by Flight Offers Price), traveller details, and contact information, and returns an order id, ticketing status, and the underlying PNR reference. It is the final step in the Self-Service flight-shopping flow before payment is captured downstream by the integrator.
Install Jentic One Beta
Connect the Flight Create Orders to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Flight Create Orders, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Famadeus.com%2Famadeus-flight-create-orders" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Famadeus.com%2Famadeus-flight-create-orders" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Flight Create Orders API.
Convert a priced Amadeus flight offer into a confirmed flight order
Generate a Passenger Name Record with the traveller and contact data submitted in the request
Capture frequent-flyer numbers and seat or meal special service requests as part of the order
Return the ticketing status and order id needed for subsequent retrieve or cancel calls
Submit fare remarks and corporate codes that adjust the fare basis at order time
Use Cases
Patterns agents use Flight Create Orders API for, with concrete tasks.
★ Confirm a Flight Booking End-to-End
After a user picks an offer from Flight Offers Search and the price is reconfirmed by Flight Offers Price, the integrator posts the offer plus traveller and contact details to /booking/flight-orders to create the actual booking. The response includes the order id and ticketing status the integrator needs to display a confirmation page and track the PNR.
POST a confirmed flight offer with one adult traveller (name, date of birth, document number) and contact email to /booking/flight-orders and return the order id.
Multi-Passenger Group Booking
Travel agencies booking 2-9 passengers on the same itinerary submit a single create-order call with an array of travellers and matching travelerPricings from the priced offer. Amadeus returns one order covering all passengers, simplifying downstream retrieval and cancellation versus issuing per-passenger orders.
Create a flight order for a family of four (two adults, two children) on the same priced offer and return the single order id covering all four travellers.
Add Frequent Flyer Numbers at Booking
Loyalty-aware integrations include frequent flyer programs in the traveller payload at create-order time so miles credit correctly without a follow-up servicing call. Each traveller can carry one or more frequent flyer entries keyed to a carrier code; Amadeus stores them on the resulting PNR and forwards them to the marketing carriers.
Create a flight order for a single traveller with a Star Alliance frequent flyer number attached to the appropriate operating carrier.
Agent Books a Flight via Jentic
An AI travel assistant that searches and prices flights through Amadeus uses the create-orders endpoint via Jentic to commit the booking once the user confirms. Jentic resolves the OAuth 2.0 client credentials, validates the request body against the operation schema, and returns a structured order id the agent can show the user.
Call jentic.search('book an Amadeus flight offer'), load the operation, and execute it with a priced offer plus traveller payload to return the new flight order id.
Key Endpoints
1 endpoints — the amadeus flight create orders api turns a priced flight offer into a confirmed booking with a passenger name record.
METHOD
PATH
DESCRIPTION
POST
/booking/flight-orders
Create a flight order from a priced flight offer
POST
/booking/flight-orders
Create a flight order from a priced flight offer
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
F
Flight Create Orders
- Non-Ready (F)0/100
72
Foundational Compliance77
Developer Experience & Jentic Compatibility56
AI-Readiness & Agent Experience94
Agent Usability100
Security0
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
72
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A-Signals: 4
87%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
77
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: A-Signals: 4
43%
Example Density
How richly the API is illustrated with examples.
89%
Example Validity
Percentage of examples that conform to their schemas.
75%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
56
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: CSignals: 4
74%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
50%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
100
Security
Trust, risk posture, and security compliance.
Grade: A+Signals: 1
100%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
0
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: FSignals: 1
0%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Flight Create Orders API by hand means running the Amadeus OAuth 2.0 client_credentials exchange, refreshing the bearer token, shaping the traveller and contact payload into the POST /booking/flight-orders body, and handling the returned PNR against the correct Amadeus host and version. Through Jentic you install once, import Flight Create Orders from the API Directory, store the Amadeus client credentials once, and your agent calls it.
Permission scoping
The priced offer and traveller details travel in the request body rather than as a resource id in the URL path, so scoping is by operation. You choose the operations the agent may call, so this booking operation is only in reach when you include it, and search, repricing, and payment operations are not included unless you add them.
Credential isolation
Your Amadeus client_id and client_secret are stored once, encrypted, by your own Jentic One instance, which runs the client_credentials exchange and injects a fresh bearer token before each booking call. The raw secret never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'book this priced Amadeus flight offer', and Jentic returns the /booking/flight-orders operation with its input schema, including the required traveller and contact shapes, so the agent creates the order without reading the Amadeus docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Flight Create Orders API through Jentic.
What authentication does the Flight Create Orders API use?
Amadeus Self-Service OAuth 2.0 client_credentials. Exchange your client_id and client_secret at https://api.amadeus.com/v1/security/oauth2/token for a bearer token, then send it in the Authorization header on the POST. Through Jentic, the credentials live in the encrypted vault and the bearer token is fetched and rotated for you, so the agent only references a scoped tool.
Can I create a flight order without first calling Flight Offers Price?
It is strongly discouraged. The /booking/flight-orders endpoint expects the exact offer payload returned by Flight Offers Price; using the raw search response often produces price or availability errors. The recommended flow is search, then price, then create order.
What are the rate limits for the Flight Create Orders API?
Amadeus Self-Service Test environment caps booking endpoints at 1 transaction per second per API key with a small monthly quota. Production limits depend on your Self-Service plan; contact Amadeus to raise quotas before launch. OAuth tokens themselves expire after roughly 30 minutes.
How do I create a flight order through Jentic?
Run pip install jentic, then call jentic.search('book an Amadeus flight offer'), load the returned operation, and execute it with a body containing the priced flight offer, travellers array, and contacts array. Jentic posts to /booking/flight-orders and returns the order id.
Does this API charge the traveller's payment method?
No. The Self-Service create-orders endpoint reserves the booking and may issue a ticket depending on the carrier, but actual payment capture is handled by the integrator outside Amadeus. Plug in your own PSP (such as Stripe or Adyen) before or after the create-order call.
How do I retrieve or cancel an order I just created?
Use the Flight Order Management API with the order id returned in the create-order response. Its GET /booking/flight-orders/{flight-orderId} retrieves the order and DELETE on the same path cancels it.
Can I limit what my agent is allowed to do with the Flight Create Orders API?
Yes. Because you run Jentic One yourself, you decide which operations your agent can call, and scoping here is by operation since the priced offer and traveller details travel in the POST /booking/flight-orders request body rather than as an id in the URL path. The create-order operation is only in reach when you include it, so an agent can commit a booking but cannot search flights, reprice offers, or capture payment unless you add those operations too. Your Amadeus client_id and client_secret stay stored on your own instance, which runs the OAuth exchange and injects the bearer token so the raw secret never reaches the agent.
GET STARTED