/sothebys/auctions/lots

POST /api/sothebys/auctions/lots

Price: 20 credits

List the lots of one Sotheby's auction by auction id or URL, in catalogue order: lot number, title, artist, estimate, current and starting bid, bid count, reserve and closing state, sold state and images.

How to use it

List a Sotheby's auction's lots by the id or url from sothebys/auctions/search. Pass a lot's id to sothebys/lots for its full catalogue entry and realized price.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• auction string required — Sotheby's auction id or auction URL (examples: "84208d43-3702-4ce2-959c-e30a8bd2c93d", "https://www.sothebys.com/en/buy/auction/2026/contemporary-curated-3"; minLength: 1)
• count integer required — Max number of lots to return (min: 1)

Response

• @type string (default: "SothebysLotCard")
• id string required
• url string nullable
• alias string nullable
• lot_number string nullable
• subtitle string nullable
• creators string nullable
• images array (default: [])
• tags array (default: [])
• session_id string nullable
• sale_number string nullable
• parcel_name string nullable
• withdrawn_state string nullable
• is_premium boolean nullable
• is_crypto_accepted boolean nullable
• estimate_low number nullable
• estimate_high number nullable
• estimate_currency string nullable
• is_estimate_on_request boolean nullable
• is_closed boolean nullable
• is_reserve_met boolean nullable
• bid_count integer nullable
• closes_at integer nullable
• current_bid number nullable
• starting_bid number nullable
• bid_currency string nullable
• bidding_type string nullable
• bidding_phase string nullable
• bidding_method string nullable
• is_sold boolean nullable
• final_price number nullable
• final_price_currency string nullable
• sold_status string nullable
• sale_price number nullable
• hammer_price 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 Sotheby's auction with a lot list 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.