/hotpepper/restaurants/reviews

POST /api/hotpepper/restaurants/reviews

Price: 5 credits

Get Hot Pepper Gourmet (ホットペッパーグルメ) restaurant reviews (口コミ) by id (strJ{id} or J{id}, or restaurant URL): author, reviewer age group and gender, rating, meal type, party size, visit scene, reserved course, visit date, text and review photos.

How to use it

Get user reviews (口コミ) of a Hot Pepper Gourmet restaurant by id ('J003433499' or 'strJ003433499') or a full restaurant URL. Each review has id, author (+author_url), age_group, gender, rating, meal (dinner/lunch), party_size, scene, reserved_course, is_reserved, visit_date, text and images.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• restaurant string required — Hot Pepper restaurant id (strJ{id} or J{id}) or a full restaurant URL (examples: "J003433499", "strJ003433499", "https://www.hotpepper.jp/strJ003433499/"; minLength: 1)
• count integer required — Max number of reviews to return (min: 1)

Response

• @type string (default: "HotpepperReview")
• id string required
• author string nullable
• author_url string nullable
• age_group string nullable
• gender string nullable
• rating number nullable
• meal string nullable
• party_size integer nullable
• scene string nullable
• reserved_course string nullable
• is_reserved boolean (default: false)
• visit_date string nullable
• text 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 — 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.