Agoda Flight Locations API

Endpoint facts

Method

GET

API path

/agoda/flights/search-locations

Auth

apiKey

Credits

3 credits/request

Platform

Agoda

Response schema

#/definitions/agoda.flightLocationSearchResponseDoc

Overview

Resolves a free-text city or airport name into IATA airport codes for flight search, with each city's direct and nearby airports. Credential-free public data from Agoda's own flight destination search. Developers commonly use this endpoint for data enrichment, monitoring, research dashboards, internal automation, and agent-native workflows that need repeatable structured public web data. Authentication uses the documented Crawlora headers, and usage is metered with the credit cost shown on this page.

Authentication

Send your scraping API key in the x-api-key header. Use the console API Keys page to rotate or select the active key.

Billing

Endpoint usage is metered in credits. The plan prices, included credits, limits, and overage rates below match the active backend billing configuration.

Credit cost

3 credits/request

Charged response

Successful 2xx responses

Infrastructure behavior

This endpoint is executed through Crawlora's managed scraping infrastructure.

• Proxy strategy: managed automatically where needed
• Browser rendering: enabled for supported targets that require rendered HTML or JavaScript execution
• Browser cluster: supported dynamic workloads can be routed through distributed browser instances
• Retry behavior: automatic retry/fallback may be used depending on endpoint type
• Challenge handling: challenged pages or unusable upstream HTML are detected and surfaced clearly when they cannot be used
• Billing: credits are charged only for successful 2xx responses
• Observability: responses include request context where available

Response behavior

- An empty or missing `keyword` returns `400` before any upstream request is made. - A query with no matches returns `200` with an empty `suggestions` list, not an error. - `city_code` is only present when the location has its own distinct city-wide booking code (e.g. Bangkok's is `BKK`, matching its single main airport). Locations with no distinct city-wide code (e.g. a city served by one airport with a different code from the city name) have an empty `city_code` — use one of `airports[].code` instead. - `airports` lists airports directly serving the location; `nearby_airports` lists nearby alternates (each with a `distance_km`), only populated for some entries. Example response: ```json { "code": 200, "msg": "OK", "data": { "keyword": "Bangkok", "count": 1, "suggestions": [ { "name": "Bangkok", "city_code": "BKK", "country_code": "TH", "country_name": "Thailand", "state_name": "Bangkok Province", "airports": [ {"code": "BKK", "name": "Suvarnabhumi Airport", "lat": 13.681108, "lng": 100.747283} ] } ] } } ```

Error behavior

Crawlora does not silently return bad data when the upstream page cannot be used.

When possible, Crawlora returns structured error context so your integration can retry, back off, or inspect the request.

Related