​
Airport Information

The Travelese Engine API uses IATA airport codes to identify airports in requests and responses. This guide provides information about airport codes and how they are used in the API.

​
IATA Airport Codes

IATA (International Air Transport Association) airport codes are three-letter codes used to identify airports worldwide. For example:

  • LHR: London Heathrow Airport
  • JFK: John F. Kennedy International Airport
  • LAX: Los Angeles International Airport
  • SIN: Singapore Changi Airport
  • DXB: Dubai International Airport

​
Using Airport Codes

Airport codes are used in various API endpoints:

  1. Flight Search: When searching for flights using the /shop/flight endpoint:

    GET /shop/flight?origin=LHR&destination=JFK

  2. Response Data: In flight segment information:

    {
  "departure": {
    "locationCode": "LHR",
    "terminal": "5"
  },
  "arrival": {
    "locationCode": "JFK",
    "terminal": "4"
  }
}

​
Major Airport Hubs

Here are some major airport hubs by region:

​
Europe

  • LHR: London Heathrow, United Kingdom
  • CDG: Charles de Gaulle, France
  • FRA: Frankfurt Airport, Germany
  • AMS: Amsterdam Schiphol, Netherlands
  • MAD: Madrid Barajas, Spain

​
North America

  • JFK: New York JFK, USA
  • LAX: Los Angeles International, USA
  • ORD: Chicago O’Hare, USA
  • YYZ: Toronto Pearson, Canada
  • MEX: Mexico City International, Mexico

​
Asia

  • SIN: Singapore Changi, Singapore
  • HKG: Hong Kong International, Hong Kong
  • NRT: Tokyo Narita, Japan
  • ICN: Seoul Incheon, South Korea
  • PEK: Beijing Capital, China

​
Middle East

  • DXB: Dubai International, UAE
  • DOH: Hamad International, Qatar
  • AUH: Abu Dhabi International, UAE
  • IST: Istanbul Airport, Turkey

​
Oceania

  • SYD: Sydney Airport, Australia
  • MEL: Melbourne Airport, Australia
  • AKL: Auckland Airport, New Zealand

​
Airport Information in Responses

When an airport appears in API responses, it typically includes:

{
  "locationCode": "LHR",      // IATA code
  "terminal": "5",            // Terminal number/letter
  "at": "2024-03-01T10:00:00" // Local time at the airport
}

​
Best Practices

  1. Validation: Always validate airport codes before making API requests
  2. Case Sensitivity: Airport codes are case-sensitive and should be uppercase
  3. Timezone Awareness: Times in responses are in the local timezone of the airport

​
Finding Airport Codes

To find the correct IATA code for an airport:

  1. Use the official IATA Airport Codes Directory
  2. Check the airport’s official website
  3. Use online flight search engines that display IATA codes

​
Common Issues

  1. Invalid Airport Codes: Using incorrect or non-existent IATA codes will result in a 400 Bad Request error
  2. Restricted Airports: Some airports may not be available through certain providers
  3. Airport Changes: Occasionally, airports may change their IATA codes or cease operations

​
Need Help?

If you need help finding the correct airport code or have questions about airport-related responses:

Was this page helpful?