/yahoo/auctions/sellers/reviews/summary

POST /api/yahoo/auctions/sellers/reviews/summary

Price: 10 credits

Get the aggregated feedback score of a Yahoo! Auctions Japan (Yahoo!オークション) seller without downloading every comment: total rating count and positive-feedback percentage, split into feedback received while selling and while buying, plus a positive/neutral/negative breakdown over the last week, month, six months, 100 transactions and 1000 transactions.

How to use it

Compact trust score for a Yahoo! Auctions Japan seller. Provide seller (the opaque id from /seller/{id}). Returns rating_count, rating_count_as_seller, rating_count_as_buyer, good_rating, good_rating_as_seller, good_rating_as_buyer (percentages) and windows — one entry per period (last_week, last_month, last_6_months, last_100, last_1000) with positive, neutral and negative counts. Use yahoo/auctions/sellers/reviews to read the individual comments.

Parameters

• access-token string required

Request body

• timeout 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)

Response

• @type string (default: "YahooAuctionsSellerRatingSummary")
• seller_id string required
• url string required
• rating_count integer nullable
• rating_count_as_seller integer nullable
• rating_count_as_buyer integer nullable
• good_rating number nullable
• good_rating_as_seller number nullable
• good_rating_as_buyer number nullable
• windows array (default: [])
  • @type string (default: "YahooAuctionsRatingWindow")
  • window string required
  • positive integer nullable
  • neutral integer nullable
  • negative 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 — Seller not found (well-formed id but no such seller on Yahoo! Auctions Japan) 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.