/housing/locations/autocomplete

POST /api/housing/locations/autocomplete

Price: 1 credit

Resolve a free-text query (locality, landmark, project, builder or city) into Housing.com location suggestions. Each suggestion carries an id, type (locality/project/landmark/developer/city), city and a locality_gid usable as the locality filter for housing/properties/search.

How to use it

Typeahead resolver for Housing.com search parameters. Pass keyword (e.g. 'Powai', 'Bandra Mumbai') and channel (buy/rent/commercial/paying_guest/plots) plus count. Returns suggestions with id, name, type (Locality/project/landmark/developer/city), sub_type, display_type, city, locality_gid (e.g. 'powai-gid', feed into housing/properties/search locality) and url. Use it to turn human input into the city + locality_gid that the search endpoints expect.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• keyword string required — Search prefix: locality, landmark, project, builder or city name (minLength: 1)
• channel string — Search channel the suggestions are scoped to (default: "buy"; one of: "buy", "rent", "commercial", "paying_guest", "plots")
• count integer required — Max number of suggestions to return (min: 1)

Response

• @type string (default: "HousingLocation")
• id string required
• name string nullable
• type string nullable
• sub_type string nullable
• display_type string nullable
• city string nullable
• locality_gid string nullable
• url string nullable

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 — The entity was not found, or a precondition failed 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.