POST /api/yahoo/auctions/sellers/reviews
Price: 10 credits
List the feedback comments left for a Yahoo! Auctions Japan (Yahoo!オークション) seller: the verdict, who left it and their own rating count, the auction it refers to, the comment text and how recently it was posted. Can be narrowed to feedback received while selling or while buying, and to positive, neutral or negative verdicts only.
Read a Yahoo! Auctions Japan seller's feedback for trust and reputation analysis. Provide seller (the opaque id from /seller/{id}) and count; optionally role (as_seller/as_buyer) and rating (positive/neutral/negative). Each result has rating (very_good/good/neutral/bad/very_bad), rating_label (the original Japanese wording), role, author and author_rating_count, item_id/item_title/item_url of the transaction, text and rated_at_label (Yahoo only publishes a relative window such as '1か月以内', never an exact date). For aggregate counts use yahoo/auctions/sellers/reviews/summary.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)seller string required — Yahoo! Auctions Japan seller id or a full seller page URL (examples: "2WZF25HbH5hVYuP5xt9wEg1CArvMM"; minLength: 1)role string nullable — Only feedback the user received while selling (as_seller) or while buying (as_buyer) (one of: "as_seller", "as_buyer")rating string nullable — Only feedback with this verdict (one of: "positive", "neutral", "negative")count integer required — Max number of results to return (examples: 25; min: 1)@type string (default: "YahooAuctionsSellerReview")rating string nullablerating_label string nullablerole string nullableauthor string nullableauthor_rating_count integer nullableitem_id string nullableitem_title string nullableitem_url string nullabletext string nullablerated_at_label string nullable422 — 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.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.