# SITA Airport Reference API MCP > SITA Airport Reference API provides access to global airport infrastructure data through your AI agent. Use it to query specific IATA codes, list all active terminals and gates at an airport, or pull a complete directory of worldwide airports registered in the SITA database. ## Overview - **Category:** data-analytics - **Price:** Free - **Tags:** airport-data, aviation, iata-codes, travel-tech, terminals, reference-data ## Description Your AI client uses this server to connect straight into SITA's global airport reference database. It’s how you pull hard, verified air transport data—the kind of stuff that runs the industry. You don't need to babysit spreadsheets; your agent handles all the querying for you. When you're building something out, you’ll use three main tools here. They let you map everything from a single gate area across the globe to every airport registered in the system. If you need to know what airports are even playable in the SITA system, you use `list_sita_airports`. This tool pulls a complete directory of every global airport they've cataloged. It gives you a master list that includes both the full name and the three-letter IATA code for each location. You start here if your project needs to know where all the action is happening. You can then take any specific airport code from that list and drill down with `get_airport_reference_details`. This function fetches the full, deep metadata packet for one single airport. You don't just get a name; you get the timezone data, the GPS coordinates, the city, the country—everything required to map it or validate its record against other systems. It’s robust data covering operational details and physical location info. For routing or passenger flow planning, you need an inventory of facilities at that specific airport. You use `list_airport_terminals` for this. This tool lists all the terminals, concourses, and gate areas tied to a known airport code. It gives you a granular breakdown of the physical infrastructure. You'll pull these details when your logic needs to know which gates are open or what specific terminal building services that particular flight path. It’s a sequence: First, you check the global list using `list_sita_airports`. Next, you get the main metadata packet for an airport code with `get_airport_reference_details`, getting all those coordinates and timezone details. Finally, if your job requires knowing where people physically walk or park, you run `list_airport_terminals` to map out every gate and concourse connected to that location. You use these three functions together to build a complete picture of global air travel infrastructure. You don't write complex SQL queries; you just tell your agent the job—like 'give me all terminals at LHR,' or 'show me the coordinates for Tokyo.' The server handles pulling those definitive, official data points back to your client. ## Tools ### get_airport_reference_details Gets full metadata for one airport using its 3-letter IATA code (e.g., LHR). ### list_sita_airports Provides a full list of every global airport registered in the SITA database. ### list_airport_terminals Lists all terminals and gate areas associated with a specific airport code. ## Prompt Examples **Prompt:** ``` Show me all the terminals at London Heathrow Airport. ``` **Response:** ``` I've retrieved the terminal information for LHR. London Heathrow has 4 active terminals: Terminal 2 (The Queen's Terminal), Terminal 3, Terminal 4, and Terminal 5. Would you like details on a specific terminal? ``` **Prompt:** ``` Get the full details for São Paulo Guarulhos airport. ``` **Response:** ``` Here are the details for GRU (São Paulo/Guarulhos International Airport): Location: Guarulhos, São Paulo, Brazil. Timezone: America/Sao_Paulo (UTC-3). IATA: GRU, ICAO: SBGR. Coordinates: -23.4356, -46.4731. Would you like to see the terminal layout? ``` ## Capabilities ### List All Global Airports Pull the full directory of every airport in the SITA system using `list_sita_airports`. ### Retrieve Full Airport Metadata Fetch complete reference data for a single airport by providing its 3-letter IATA code, using `get_airport_reference_details`. ### List Terminal and Gate Areas Get an inventory of all terminals, concourses, and gates belonging to a specific airport code via `list_airport_terminals`. ## Use Cases ### A travel product needs to validate a city's airport. The engineer asks their agent: 'What’s the IATA code and timezone for Dallas?' The agent runs `get_airport_reference_details`. Instead of getting a vague response, they get structured data (coordinates, timezone) immediately, letting them save the user record without any guesswork. ### A logistics company maps out cargo routes. The planner needs to know every possible stop. They run `list_sita_airports` first to get a comprehensive list of all global hubs. Then, they can loop through the codes and call `get_airport_reference_details` for each one, building a complete network map. ### A passenger app needs terminal instructions. The user asks: 'Where do I find Gate B12 at Heathrow?' The agent recognizes this needs structural data and runs `list_airport_terminals` for LHR. It returns the specific Terminal 3 details, solving a complex physical routing problem in seconds. ### A database migration requires global airport codes. The developer doesn't know which airports exist. They run `list_sita_airports` to get the definitive list of all registered codes, ensuring their new system covers every known location before they even start building features. ## Benefits - You get accurate facility mapping. Using `list_airport_terminals`, you pull a full list of concourses and gates for any major hub, which is critical when building passenger routing tools. - No more guesswork on location data. The `get_airport_reference_details` tool delivers exact coordinates, timezones, and country details in one call—perfect for map-based services. - Build a global directory instantly. If you need to know every airport that exists in the SITA system, running `list_sita_airports` gives you the master list right away. - Chain calls efficiently. You can first run `list_sita_airports` to get codes, then immediately use `get_airport_reference_details` on a specific code to pull the next layer of data. - Handle complex inputs simply. Your agent manages which tool runs and what parameters it needs. You just ask: 'Tell me about Paris.' - Stop fighting bad APIs. This server uses SITA's official, industry-leading database, giving you reliable facts for travel tech products. ## How It Works The bottom line is, you talk to your AI client like it’s a person, but the server handles all the complex lookups against SITA’s live database. 1. First, subscribe to the server. Then, register at the SITA Developer Portal to get your API Key. 2. You pass a natural language request to your AI client (e.g., 'What are the terminals at JFK?'). 3. Your agent executes the appropriate tool call (`list_airport_terminals`) using your credentials and returns structured data detailing the airport's facilities. ## Frequently Asked Questions **How do I find all airports using list_sita_airports?** You just ask your agent to run `list_sita_airports`. This tool immediately returns a comprehensive directory of every global airport registered in the SITA database, giving you a master list of codes and names. **Does get_airport_reference_details give me coordinates?** Yes. The `get_airport_reference_details` tool returns comprehensive metadata, including precise latitude/longitude coordinates, timezone data, city, and country for the specified airport code. **What is the difference between list_sita_airports and get_airport_reference_details?** They serve different purposes. Use `list_sita_airports` when you need a full directory to search through codes. Use `get_airport_reference_details` when you already have the code (like JFK) and need all its specific details. **Can list_airport_terminals show me gate capacity?** The tool lists all terminals, concourses, and gate areas for an airport. While it doesn't report current *capacity*, it gives you the full inventory of every assigned gate area. **What IATA codes can I use with these tools?** You must provide a 3-letter IATA code (like LHR or GRU). The tool requires this specific format to correctly identify the airport in the SITA database. **How do I authenticate my calls to get_airport_reference_details?** You must acquire an API Key from the SITA Developer Portal. Your AI client passes this key in the request headers for every call. This step authenticates your session and grants access to the live reference database. **What happens if I provide an invalid code when calling list_airport_terminals?** The tool returns a specific error message that indicates failure, preventing system crashes. You must pass a valid 3-letter IATA code for the target airport. The agent will receive a structured 'Code Not Found' response. **How can I use results from list_sita_airports with get_airport_reference_details?** You chain the tools by taking an IATA code found via `list_sita_airports` and passing it as a direct argument to `get_airport_reference_details`. This allows you to query metadata for multiple airports in one workflow. **What format are airport codes in?** The API uses standard 3-letter IATA airport codes (e.g., 'LHR' for London Heathrow, 'JFK' for New York JFK, 'GRU' for São Paulo Guarulhos). **Is this a read-only API?** Yes, all 3 tools are strictly read-only queries. The integration retrieves reference data and cannot modify anything in the SITA database.