Start with a complete search query
A useful flight API request describes the route, travel dates, passengers, cabin class, display currency, locale, point of sale, result limit, and acceptable cache age. Flight MCP validates those fields before it reads cache data or contacts an upstream provider.
Airport codes use three-letter IATA codes such as HND and SFO. Dates use ISO YYYY-MM-DD. Add returnDate for a round trip; omit it for a one-way search.
curl --request POST \
https://flight-mcp.com/v1/flights/search \
--header "Authorization: Bearer $FLIGHT_MCP_API_KEY" \
--header "Content-Type: application/json" \
--data '{
"origin": "HND",
"destination": "SFO",
"departureDate": "2026-09-18",
"returnDate": "2026-09-25",
"adults": 1,
"cabinClass": "economy",
"currency": "JPY",
"locale": "ja-JP",
"pointOfSaleCountry": "JP",
"maxResults": 20,
"cacheTtlSeconds": 300
}'Understand localization fields
currency controls the requested price currency. locale controls language and regional formatting preferences. pointOfSaleCountry identifies the market from which the search is made. They are related but not interchangeable: a Japanese point of sale can still request another supported currency or locale.
Use JPY, ja-JP, and JP when you want Japanese-market results expressed in yen and localized for Japanese users.
Work with normalized offers
The response returns up to 100 offers ordered by total price. Each offer has a stable response shape with a price, cabin class, one or more itineraries, segments, carrier information, flight number, timestamps, stops, and duration. Your application does not need separate parsing logic for each enabled data source.
Prices change frequently, so treat an offer as search information rather than a reservation. Display the response fetch time and refresh the search before a user makes a purchase decision.
Handle cache and usage metadata
The response metadata tells you whether the result came from Redis, when it expires, how long the request took, and how much monthly quota remains. A cache hit is not counted as a billable plan call. A cache miss that successfully fetches new provider data consumes one monthly call.
For the exact request and response fields, status codes, and error model, continue to the Flight MCP API documentation.