This page will help you get started with the Seats.aero partner API.
The Seats.aero partner API allows you to instantly query redemption availability across all major airline alliances. The partner API can instantly quote pricing and availability for over 70,000 routes and perform live searches on any route across 20 different mileage programs.
The Seats.aero partner API can be used by Pro users for non-commercial purposes and only by written agreement for commercial use. Please contact [email protected] with a company email address and detailed use case information to learn about potential commercial options, although note many use cases are not supported.
MCP Server
Seats.aero also offers a Model Context Protocol (MCP) server at https://seats.aero/mcp for AI assistants such as Claude and ChatGPT. It lets you search award flights, explore points transfers, and manage award alerts through your assistant.
Public searches work without a Seats.aero account. Connect your Pro account via OAuth for full search access, live searches, and alert management. See the MCP setup guide to get started.
Authorization
You will need to send your API key in the Partner-Authorization header for all requests to the partner API.
Commercial Users
You will receive an API key from the Seats.aero team.
Pro Users
Seats.aero Pro users may be able to access the partner API for up to 1,000 API calls per day at no cost. Pro users can generate their personal API key via the API tab on their personal settings page. The partner API is governed by the Seats.aero terms of use, which prohibit commercial use of our APIs without written permission.
Not all Pro users can access the partner API key or retrieve an API key. We may limit access to the API by geographical location or for any reason in our sole discretion.
Your API key also works with the Rooms.aero API for hotel award availability. Rooms.aero has its own quota of 1,000 calls per day, separate from the Seats.aero quota.
Content Types
The Seats.aero API works entirely in JSON; all responses will be in JSON. For GET requests, you should send request parameters in query parameters. For POST requests, you should send a JSON body with an application/json content type.