Amadeus Seatmap Display
Browse all Amadeus APIs✓ Official Vendor SpecE CommerceStorefrontoauth22 EndpointsREST
For Agents
Render an aircraft cabin map for a flight offer or order, with per-seat coordinates, characteristics, prices, and availability for in-flow seat selection.
Use for: Retrieve the seat map for a flight order, Get the cabin layout for a specific flight offer before booking, Find all available window seats on a flight, List exit-row seats with extra legroom
Not supported: Does not commit bookings, charge for upgrades, or change seat assignments — use for retrieving and rendering cabin seat maps only.
The Amadeus Seatmap Display API returns the cabin layout and per-seat metadata for a flight, enabling the seat-selection step of a booking flow. Two endpoints cover the common patterns: a GET keyed on a confirmed flight order id, and a POST that accepts an in-progress flight offer and returns the seat map before the booking is committed. Each seat in the response includes coordinates, characteristics (window, aisle, exit row, extra legroom), availability, and applicable price.
Install Jentic One Beta
Connect the Seatmap Display to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Seatmap Display, 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
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 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 Seatmap Display API.
Retrieve the seat map for a flight by flightOrderId
Generate a seat map from an in-progress flight offer payload via POST before booking
Surface per-seat coordinates, row, and column for cabin rendering
Expose seat characteristics — window, aisle, exit row, extra legroom, restricted
Return per-seat availability and price so the UI can disable or charge for premium seats
Use Cases
Patterns agents use Seatmap Display API for, with concrete tasks.
★ In-flow seat selection during booking
Render the seat map mid-booking after the user has selected a flight offer but before committing the order. POST the offer payload to Seatmap Display, parse the returned cabin into a grid, and let the user pick a seat with live pricing and availability. This is the standard way to add a seat-selection step to a custom booking funnel built on Amadeus Flight Offers Search.
POST /shopping/seatmaps with a flight offer payload and return all seats marked AVAILABLE with characteristic 'WINDOW'.
Post-booking seat upgrade
After a flight is booked, allow the passenger to upgrade their seat assignment. Use the GET variant keyed on flightOrderId to retrieve the live seat map for an existing reservation, surface available premium seats with their prices, and present an upgrade flow. Combine with Flight Order Management to update the seat assignment on the order.
Call GET /shopping/seatmaps with flight-orderId and return all seats with characteristic 'EXIT_ROW' that are AVAILABLE.
Seat preference matching
For corporate travel platforms with stored seat preferences (window, aisle, no middle seats), automatically pre-select the best available seat on a freshly booked flight. Call Seatmap Display with the flight order, score each available seat against the traveller's profile, and POST the chosen seat back to the order. The seat characteristics array makes preference matching straightforward.
Given a stored preference of 'aisle, no middle, no exit row', call Seatmap Display and return the lowest-row aisle seat that matches.
AI agent seat assistant
An AI agent helping a traveller pick a seat uses Seatmap Display to ground its recommendation in real cabin data rather than guessing. The agent calls Jentic to discover the operation, executes it for the user's flight offer, and presents the best 3 seats matching the user's preferences with live prices. This grounds AI seat advice in actual availability.
Use Jentic to search 'get a flight seat map', execute Seatmap Display for the user's flight offer, and return the top 3 available aisle seats sorted by ascending price.
Key Endpoints
2 endpoints — the amadeus seatmap display api returns the cabin layout and per-seat metadata for a flight, enabling the seat-selection step of a booking flow.
METHOD
PATH
DESCRIPTION
GET
/shopping/seatmaps
Get the seat map for a flightOrderId
POST
/shopping/seatmaps
Generate a seat map from a flight offer payload
GET
/shopping/seatmaps
Get the seat map for a flightOrderId
POST
/shopping/seatmaps
Generate a seat map from a flight offer payload
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Amadeus OAuth2 client_id and client_secret are stored encrypted in the Jentic vault. Agents receive scoped bearer tokens; the client secret never enters the agent's context.
Intent-based discovery
Agents search by intent ('get a flight seat map') and Jentic returns the GET and POST Seatmap Display operations with their flightOrderId and offer-payload schemas.
Time to first call
Direct Amadeus integration: 2-3 days for OAuth, offer payload handling, and cabin rendering. Through Jentic: under 1 hour — search, load, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Seatmap Display API through Jentic.
What authentication does the Seatmap Display API use?
OAuth 2.0 client credentials. Exchange your Amadeus API key and secret for a bearer access token, then pass it as the Authorization header on each call. Through Jentic, the client secret stays encrypted in the vault and the agent only ever receives a scoped token.
When should I use the GET vs the POST variant?
Use GET /shopping/seatmaps with a flightOrderId for an already-booked itinerary, for example to support a post-booking seat upgrade flow. Use POST /shopping/seatmaps with a flight offer payload during the booking funnel — before the order has been committed — to render the seat map for the offer the user has just selected.
What seat characteristics are returned?
Each seat includes its row and column coordinates and a characteristics list — common values include WINDOW, AISLE, EXIT_ROW, EXTRA_LEGROOM, and RESTRICTED. The response also includes per-seat availability and price, so a UI can both disable unavailable seats and charge for premium ones.
What are the rate limits for the Seatmap Display API?
Amadeus enforces per-second and per-month transaction quotas that vary by environment. The test environment (test.api.amadeus.com/v1) has low quotas suitable for development; production limits are configured in your Amadeus for Developers contract.
How do I get a flight seat map through Jentic?
Install with pip install jentic, then search 'get a flight seat map' to discover the Seatmap Display operations. Load the GET or POST schema and execute. Jentic returns the parsed cabin map ready to render. Get started at https://app.jentic.com/sign-up.
Does test.api.amadeus.com return seat maps for every flight?
No. The test environment is a subset of production. If a query returns no results, retry with a major-city flight (e.g. routes through LON or NYC) or move to production for full coverage.
GET STARTED