/makemytrip/places/search

POST /api/makemytrip/places/search

Price: 1 credit

Resolve a city, airport name or IATA code into MakeMyTrip place identifiers via autosuggest. Returns ranked matches with the IATA code (city metro code such as NYC, or a specific airport code such as JFK), city and airport name, country and country code, the MakeMyTrip locus code and, for multi-airport cities, the list of nested airports with their distance from the city centre. Covers airports and cities worldwide.

How to use it

Autosuggest MakeMyTrip places by query (a city name, airport name or IATA code). Returns matches with iata_code, city, airport_name, country, country_code, locus_code and, for metro cities, nested airports (each with iata_code, city, airport_name and distance_info).

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• query string required — City, airport name or IATA code to resolve (examples: "mumbai"; minLength: 1)
• count integer required — Max number of results (min: 1)

Response

• @type string (default: "MakemytripPlace")
• iata_code string nullable
• city string nullable
• airport_name string nullable
• country string nullable
• country_code string nullable
• locus_code string nullable
• distance_info string nullable
• airports array (default: [])

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — No places matched the given query Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.