Opodo Locations API Documentation Pass one or more IATA codes in repeated iatas parameters, or a keyword in query. Ids such as geoNodeId are returned unchanged and can be used as origin and destination in flight search. Prices are not part of this endpoint.
Run this endpoint
Endpoint
Parameters
Start with the required fields, then add optional filters only when your use case needs them.
Runnable path
This endpoint has no required query parameters.
2 optional filters available.
array
Optional
One or more three-letter IATA codes, repeated, for example iatas=BER and iatas=LHR. Required unless query is given.
["example"]
string
Optional
City or airport name, 2 to 100 characters. Required unless iatas is given.
coffee shops
Response Schema
Example response fields are illustrative; inspect the JSON before integrating.
Example response fields
Scan these fields before integrating.
data
success
{
"data": {
"mode": "iata",
"locations": [
{
"city": "Berlin",
"iata": "BER",
"name": "Berlin Brandenburg",
"coordinates": {
"latitude": 52.36,
"longitude": 13.5
},
"geo_node_id": 9654,
"country_code": "DE",
"geo_node_type": "CITY"
}
]
},
"success": true
}
Errors
Handle these documented responses before retrying or showing customer-facing failures.
HTTP UPSTREAM_UNAVAILABLE
Opodo data is temporarily unavailable. Please retry.
HTTP PARSER_DRIFT
The upstream response shape changed.
HTTP NOT_FOUND
The requested location was not found.
Generate Code with AI
Copy a ready-made prompt with all the endpoint details, parameters, and example responses. Paste it into ChatGPT, Claude, or any AI assistant to instantly generate working code.
Try It Live
Test this endpoint in our interactive playground with real data.