/tabelog/restaurants/search

POST /api/tabelog/restaurants/search

Price: 5 credits

Search Tabelog (食べログ) restaurants by keyword and/or genre with optional filters: prefecture, budget range, private room, credit card, parking and sort order. Returns restaurant cards with name, rating, review and saved counts, area/station, genres, budgets and images.

How to use it

Search Tabelog (食べログ) restaurants. Provide keyword and/or genre (Japanese cuisine categories). Optional: pref (e.g. 'tokyo', 'osaka'), budget_min/budget_max (JPY per person), budget_for_lunch, private_room, card_ok, parking; sort by standard/rating/review_count/newest. Each result has id ('{pref}/A{area1}/A{area2}/{id}'), url, name, rating (Tabelog ★), review_count, saved_count, area, station (with distance), genres, budget_dinner/budget_lunch, pr_title and image/images.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• keyword string nullable — Search keyword (examples: "寿司", "ramen", "イタリアン")
• pref string nullable — Prefecture/area slug to scope the search (examples: "tokyo", "osaka")
• genre string nullable — Restaurant genre filter (one of: "RC0103", "RC0104", "RC0105", "RC0106", "RC0107", "RC0108", "RC0109", "RC0111", "RC0121", "RC0123", "RC0124", "RC0125", "RC0201", "RC0209", "RC0219", "RC0220", "RC0301", "RC0303", "RC0305", "RC0306", "RC0307", "RC0308", "RC0309", "RC0310", "RC0402", "RC0403", "RC0404", "RC0411", "RC0412", "RC0499", "RC1201", "RC1203", "RC1205", "RC1302", "RC1401", "RC1402", "RC1404", "RC1406", "RC1408", "RC2101", "RC2102", "RC2103", "RC2104", "RC2105", "RC9801", "RC9802", "RC9803", "RC9804", "RC9805", "RC9806", "RC9807", "RC9808", "RC9809", "RC9811", "RC9812", "RC02", "RC04", "RC13")
• budget_min integer nullable — Minimum per-person budget (JPY) (min: 0)
• budget_max integer nullable — Maximum per-person budget (JPY) (min: 0)
• budget_for_lunch boolean — Apply the budget filter to lunch instead of dinner (default: false)
• private_room boolean — Only restaurants with a private room (default: false)
• card_ok boolean — Only restaurants accepting credit cards (default: false)
• parking boolean — Only restaurants with parking (default: false)
• sort string — Sort order (default: "standard"; one of: "standard", "rating", "review_count", "newest")
• count integer required — Max number of results to return (min: 1)

Response

• @type string (default: "TabelogSearchCard")
• id string required
• url string required
• name string nullable
• rating number nullable
• review_count integer nullable
• saved_count integer nullable
• area string nullable
• station string nullable
• genres array (default: [])
• budget_dinner string nullable
• budget_lunch string nullable
• pr_title string nullable
• image string nullable
• images 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 — 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.