POST /api/caloo/reviews
Price: 20 credits
Get one patient review from Caloo (病院口コミ検索カルー): full text, rating, author relation, age group and gender, specialty and disease tags, visit and posting period, wait time, fee, helpful votes, review photos and the hospital's reply
Pass the hospital_id and id of a review from caloo/reviews/search or caloo/hospitals/reviews.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)hospital string required — Caloo hospital id or hospital URL (examples: "4130005266", "https://caloo.jp/hospitals/detail/4130005266"; minLength: 1)review_id string required — Caloo review id or review URL (examples: "486048", "https://caloo.jp/hospitals/detail/4130005266/reviews/486048"; minLength: 1)@type string (default: "CalooReview")id string requiredkind string required (one of: "review", "postcard")hospital_id string requiredhospital_name string nullablehospital_area string nullableurl string nullabletext string nullablerating number nullableauthor_name string nullableauthor_relation string nullableauthor_age_group string nullableauthor_gender string nullableauthor_review_count integer nullabletags array (default: [])@type string (default: "CalooTaxon")code string requiredname string nullablegroup string nullablespecialty_name string nullabledisease_name string nullablevisit_year integer nullablevisit_month integer nullableposted_year integer nullableposted_month integer nullableposted_date integer nullablevisit_type string nullablewait_time string nullablemedicine string nullablefee string nullablefee_note string nullabletreatment_category string nullabletreatment_method string nullablehelpful_count integer nullablevote_count integer nullableimage string nullableimages array (default: [])image_captions array (default: [])reply_text string nullable422 — hospital or review_id is not a Caloo id or URL 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 Caloo review under that hospital id and review id 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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.