/liveauctioneers/price_results

POST /api/liveauctioneers/price_results

Price: 1 credit

Get the LiveAuctioneers price-result summary for a lot title alias: how many lots sharing that alias sold, their lowest, average, median and highest hammer price, a representative lot and its category page.

How to use it

Pass a /price-result/ URL, or the alias at the end of a lot's URL after the id, to price a kind of object across past sales. The representative item_id is one of the sold lots, not necessarily the lot the alias came from.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• alias string required — Price-result page URL or its alias (examples: "https://www.liveauctioneers.com/price-result/a-pair-of-huanghuali-horseshoe-back-folding-armchairs/", "a-pair-of-huanghuali-horseshoe-back-folding-armchairs"; minLength: 1)

Response

• @type string (default: "LiveAuctioneersPriceResult")
• alias string required
• url string nullable
• sold_lot_count integer nullable
• sale_price_min number nullable
• sale_price_avg number nullable
• sale_price_median number nullable
• sale_price_max number nullable
• item_id string nullable
• item_url string nullable
• category_url string 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 sold lots are recorded under this alias. 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.