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://jentic.com/install.sh?src=apis&api=%2Fapis%2Famadeus.com%2Famadeus-flight-order-management" | sh

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-order-management" | 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

Confirm ticketing status before triggering downstream payment or fulfilment steps

GET STARTED

Start building with Flight Order Management API

Explore with Jentic One

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?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring Flight Order Management by hand means learning the Amadeus Self-Service OAuth 2.0 client_credentials flow, refreshing the bearer token before each servicing call, picking the test or production host, and threading the stored flight-orderId onto both the GET and DELETE calls. Through Jentic you install once, import Flight Order Management from the API Directory, store the client_id and client_secret once, and your agent calls it.

Permission scoping

Amadeus puts the order id in the URL path (/booking/flight-orders/{flight-orderId}), so a rule can pin your agent to a single flight order: it can retrieve that order and nothing else. You choose the operations it may call, so the destructive DELETE that cancels the order is not included unless you add it.

Credential isolation

Your Amadeus client_id and client_secret are stored once, encrypted, by your own Jentic One instance, which runs the OAuth exchange and injects a fresh bearer token at execution time. The secret never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'retrieve an Amadeus flight order' or 'cancel an Amadeus flight order', and Jentic returns the matching operation with the flight-orderId path parameter described in its input schema.

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.

Can I limit what my agent is allowed to do with the Flight Order Management API?

Yes. Because you run Jentic One yourself, your own rules decide which of this API's two operations your agent can call, so you can grant the read-only GET on /booking/flight-orders/{flight-orderId} while excluding the destructive DELETE that cancels an order. Since Amadeus puts the order id in the URL path, a rule can also pin the agent to a single flight order, letting it retrieve that one order and nothing else. Your Amadeus client_id and client_secret stay stored and encrypted on your instance, and the agent only ever supplies intent and the flight-orderId.

Amadeus Flight Order Management

Browse all Amadeus APIs

AI ReadinessAI-Aware (A-)72/100

See full scorecard

Official vendor OpenAPI document · agent-readyE 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.

Use for: Retrieve the Amadeus flight order I just created, Cancel flight order eJzTd9d3MQ before the void window closes, Get the PNR reference for an existing flight order, I want to look up the ticketing status of a flight order

Not supported: Does not search for flights, reconfirm prices, or create new orders - use only to retrieve or cancel an existing Amadeus flight order by id.

The Amadeus Flight Order Management API retrieves and cancels flight orders previously created via Flight Create Orders. The two endpoints - GET and DELETE on /booking/flight-orders/{flight-orderId} - let an integrator pull the full order state including travellers, segments, ticketing status, and PNR reference, or cancel the order within the airline's void window. It is the post-booking servicing layer of the Amadeus Self-Service flight stack.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

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.

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.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: A-Signals: 4

44%

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.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: B-Signals: 4

74%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

67%

Summary Coverage

Coverage of summaries across operations/tags/info.

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).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: C-Signals: 1

50%

Descriptive Richness

Clarity and depth of descriptions across API elements.

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

Amadeus Flight Order Management

Jentic AI Readiness Score

Flight Order Management

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness