/opentable/restaurants/autocomplete

POST /api/opentable/restaurants/autocomplete

Price: 10 credits

Autocomplete an OpenTable query into location and restaurant suggestions. Location suggestions carry metro/macro/neighborhood ids and coordinates; restaurant suggestions carry the restaurant id, name and coordinates.

How to use it

Autocomplete a free-text query (location or restaurant name) on OpenTable. Each suggestion has id, type (Location or Restaurant), subtype (Metro/Macro/LegacyHood for locations), name, metro_id, metro_name, macro_id, macro_name, neighborhood_name, country, country_id, latitude and longitude. Use it to resolve a place or to find restaurants by name.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• query string required — Free-text query: a location (city, metro, neighborhood) or a restaurant name (examples: "New York", "Capital Grille", "Brooklyn"; minLength: 1)
• count integer required — Max number of suggestions to return (min: 1)

Response

• @type string (default: "OpentableSuggestion")
• id string required
• type string required
• subtype string nullable
• name string required
• metro_id integer nullable
• metro_name string nullable
• macro_id integer nullable
• macro_name string nullable
• neighborhood_name string nullable
• country string nullable
• country_id string nullable
• latitude number nullable
• longitude number 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 — No suggestions found for the 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.