Amadeus Flight Order Management

Name: Flight Order Management API
Brand: Flight Order Management
Availability: InStock

✓ Official Vendor SpecE CommerceOrder Managementoauth22 EndpointsREST

For Agents

Retrieve or cancel an existing Amadeus flight order by id, returning full PNR detail or confirming the cancellation an agent has been asked to perform.

Install Jentic One Beta

Connect the Flight Order Management to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Flight Order Management, 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.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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 Order Management API.

Retrieve a flight order by id including travellers, segments, and ticketing status

Cancel a flight order within the airline's void window using the order id

Read the associated PNR reference from a previously created order

GET STARTED

Start building with Flight Order Management API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Flight Order Management API for, with concrete tasks.

★ Post-Booking Order Lookup

After a booking, the integrator stores the order id returned by Flight Create Orders and uses GET /booking/flight-orders/{flight-orderId} to display the booking summary on a 'manage my booking' page. The response carries traveller details, segments, ticketing status, and the underlying PNR reference, so a single call hydrates the entire view.

GET /booking/flight-orders/{flight-orderId} for the order id stored at booking time and return travellers, segments, and ticketing status.

Self-Service Cancellation Within Void Window

Travel sites that allow self-service cancellation call DELETE /booking/flight-orders/{flight-orderId} during the airline's void window (typically 24 hours after booking for many carriers). A 200 response confirms the cancellation; afterwards, the integrator handles refund processing through its own PSP and notifies the customer.

Issue DELETE /booking/flight-orders/{flight-orderId} for an order created in the past 24 hours and confirm the cancellation succeeded.

Ticketing Status Polling

For carriers that ticket asynchronously, the integrator polls GET /booking/flight-orders/{flight-orderId} on a low-frequency schedule until the ticketing status moves from PENDING to TICKETED. Once ticketed, the integrator triggers downstream fulfilment such as adding the e-ticket to a wallet pass or sending the customer their itinerary email.

Poll GET /booking/flight-orders/{flight-orderId} every 60 seconds for up to 10 minutes and stop when ticketingStatus is TICKETED.

Agent-Driven Booking Management via Jentic

An AI travel concierge handling 'cancel my Tokyo flight' uses Jentic to call Flight Order Management's DELETE endpoint with the stored order id, then confirms the cancellation to the user. Jentic resolves OAuth and validates the order id parameter, so the agent only declares intent and supplies the id.

Call jentic.search('cancel an Amadeus flight order'), load the operation, and execute it with the stored flight-orderId to delete the order.

Key Endpoints

2 endpoints — the amadeus flight order management api retrieves and cancels flight orders previously created via flight create orders.

METHOD

PATH

DESCRIPTION

GET

/booking/flight-orders/{flight-orderId}

Retrieve a flight order by id

DELETE

/booking/flight-orders/{flight-orderId}

Cancel a flight order by id

GET

/booking/flight-orders/{flight-orderId}

Retrieve a flight order by id

DELETE

/booking/flight-orders/{flight-orderId}

Cancel a flight order by id

Why Jentic?

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

Credential isolation

Amadeus client_id and client_secret are stored encrypted in the Jentic vault. Jentic runs the OAuth 2.0 client_credentials exchange and refreshes the bearer token automatically before each retrieve or cancel call.

Intent-based discovery

Agents search Jentic by intent ('retrieve an Amadeus flight order' or 'cancel an Amadeus flight order') and Jentic returns the corresponding operation with the flight-orderId path parameter described in the input schema.

Time to first call

Direct Amadeus integration: 1-2 days for OAuth and post-booking servicing flow. Through Jentic: under 30 minutes — search, load, execute.

FAQs

Specific to using Flight Order Management API through Jentic.

What authentication does the Flight Order Management API use?

Amadeus Self-Service OAuth 2.0 client_credentials. Exchange client_id and client_secret at https://api.amadeus.com/v1/security/oauth2/token for a bearer token and pass it in the Authorization header on both GET and DELETE calls. Through Jentic, the credentials live in the encrypted vault and the token is rotated for you on each servicing call.

Can I cancel an order outside the airline's void window?

No. DELETE /booking/flight-orders/{flight-orderId} only succeeds within the carrier's void window — typically 24 hours after booking for many carriers, sometimes shorter or longer depending on fare rules. After the window closes, refunds and changes must go through the carrier's normal cancellation channel.

What are the rate limits for the Flight Order Management API?

Amadeus Self-Service Test caps booking-management endpoints at 1 transaction per second per API key with a monthly quota; Production limits scale with your Self-Service plan tier. Bearer tokens themselves expire after roughly 30 minutes.

How do I retrieve or cancel an order through Jentic?

Run pip install jentic, then call either jentic.search('retrieve an Amadeus flight order') or jentic.search('cancel an Amadeus flight order'), load the corresponding operation, and execute it with the flight-orderId path parameter. Jentic handles the OAuth exchange against the appropriate /booking/flight-orders/{flight-orderId} call.

Is the order id returned by Create Orders the same one I use here?

Yes. The id field on the Flight Create Orders response is exactly the {flight-orderId} expected by both endpoints in this API. Persist it at booking time so you can retrieve or cancel later.

Does cancellation refund the customer automatically?

No. The DELETE endpoint releases the booking and any held seats with the carrier, but payment refunds are handled by the integrator's own payment service provider (Stripe, Adyen, or similar). Trigger the refund explicitly after the DELETE returns success.

Amadeus Flight Order Management

Connect the Flight Order Management to your agent

Capabilities

Start building with Flight Order Management API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs