/jmty/users/reviews

POST /api/jmty/users/reviews

Price: 1 credit

Read the reviews a Jimoty (jmty.jp) member has received. Every review names the counterparty, states whether they were the poster or the enquirer on the deal, links to the listing the deal was about, and carries the good, neutral or bad rating with its free-text comment and timestamp. Because the rating is tied to a concrete listing, this is the trail that shows what a Japanese local-classifieds seller actually traded and how counterparties judged it; the rating filter isolates the negative feedback. Where the reviewed member answered the review, that reply comes back with it.

How to use it

List reviews received by a Jimoty member. user accepts the 24 character hexadecimal profile id or the full profile URL, count is required. rating optionally narrows to good, normal or bad. author_role tells whether the reviewer was the poster (投稿者) or the enquirer (問い合わせ者) of the linked deal, and listing.key feeds jmty/listings. reply carries the answer the reviewed member wrote back, which professional sellers post on nearly every review and private members almost never do.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• user string required — Profile id or its full jmty.jp profile URL (examples: "563091fb03cb6f093c00059e", "https://jmty.jp/profiles/563091fb03cb6f093c00059e")
• rating string nullable — Keep only reviews carrying this rating (one of: "good", "normal", "bad")
• count integer required — Max number of reviews to return (min: 1; max: 10000)

Response

• @type string (default: "JmtyUserReview")
• author_id string nullable
• author_name string nullable
• author_image string nullable
• author_url string nullable
• author_role string nullable
• rating string nullable
• text string nullable
• listing object nullable
  • @type string (default: "JmtyUserReviewListing")
  • key string nullable
  • listing_title string nullable
  • vertical_label string nullable
  • url string nullable
• reply object nullable
  • @type string (default: "JmtyUserReviewReply")
  • author_name string nullable
  • author_role string nullable
  • text string nullable
  • created_at integer nullable
• created_at integer 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 jmty.jp profile with this id exists 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.