/invaluable/auction_houses/reviews

POST /api/invaluable/auction_houses/reviews

Price: 5 credits

List buyer reviews of one Invaluable auction house: star rating, title, text, date, author, verified-buyer badge, votes, answers about shipping and delivery, and sub-ratings such as lot description, communication and payment.

How to use it

Read what buyers say about an auction house; the overall rating and review count are on invaluable/auction_houses.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• auction_house string required — Invaluable auction house id or URL (examples: "8RA3GB6FWF", "https://www.invaluable.com/auction-house/abell-auction-8ra3gb6fwf/"; minLength: 1)
• count integer required — Max number of results (min: 1)

Response

• @type string (default: "InvaluableReview")
• id string required
• auction_house_id string nullable
• author string nullable
• author_id string nullable
• is_verified_buyer boolean nullable
• is_incentivized boolean nullable
• rating number nullable
• text string nullable
• language string nullable
• sentiment number nullable
• created_at integer nullable
• up_vote_count integer nullable
• down_vote_count integer nullable
• answers array (default: [])
  • @type string (default: "InvaluableReviewAnswer")
  • question string nullable
  • answer string nullable
• scores array (default: [])
  • @type string (default: "InvaluableReviewScore")
  • name string nullable
  • rating number 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 Invaluable auction house exists at this id or URL. 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.