/tabelog/restaurants

POST /api/tabelog/restaurants

Price: 5 credits

Get full Tabelog (食べログ) restaurant details by {pref}/A{area1}/A{area2}/{id} (or restaurant URL): name, address, geo, cuisines/genres, access directions, price range, rating/score, review and saved counts, nearest station, budgets, awards, opening hours, payment methods, service charge, seats, amenity features and remarks.

How to use it

Fetch a single Tabelog (食べログ) restaurant by composite id '{pref}/A{area1}/A{area2}/{id}' (e.g. 'tokyo/A1301/A130101/13002457') or a full restaurant URL. Returns name, address (street/locality/region/postal_code/country), latitude/longitude, cuisines, genres, price_range, rating (aggregate), score (Tabelog ★), review_count, saved_count, nearest_station, access (transport directions), budget_dinner/budget_lunch, awards (百名店), is_reservable, open_hours, payment_methods, service_charge, seats, has_private_room, has_charter, is_non_smoking, has_parking, space/drink/food features, usage_scenes, services, remarks, homepage_url and social_links.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• restaurant string required — Tabelog restaurant as {pref}/A{area1}/A{area2}/{id} or a full restaurant URL (examples: "tokyo/A1301/A130101/13002457", "https://tabelog.com/tokyo/A1301/A130101/13002457/"; minLength: 1)

Response

• @type string (default: "TabelogRestaurant")
• id string required
• url string required
• name string nullable
• image string nullable
• address object nullable
  • @type string (default: "TabelogRestaurantAddress")
  • street string nullable
  • locality string nullable
  • region string nullable
  • postal_code string nullable
  • country string nullable
• latitude number nullable
• longitude number nullable
• price_range string nullable
• cuisines array (default: [])
• genres array (default: [])
• access string nullable
• telephone string nullable
• rating number nullable
• score number nullable
• review_count integer nullable
• saved_count integer nullable
• nearest_station string nullable
• budget_dinner string nullable
• budget_lunch string nullable
• awards array (default: [])
• is_reservable boolean nullable
• open_hours string nullable
• payment_methods array (default: [])
• seats string nullable
• has_private_room boolean nullable
• has_charter boolean nullable
• is_non_smoking boolean nullable
• has_parking boolean nullable
• service_charge string nullable
• remarks string nullable
• space_features array (default: [])
• drink_features array (default: [])
• food_features array (default: [])
• usage_scenes array (default: [])
• services array (default: [])
• homepage_url string nullable
• social_links 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 — Restaurant not found (well-formed id but the restaurant page does not exist) 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.