/sothebys/auctions

POST /api/sothebys/auctions

Price: 10 credits

Get one Sotheby's auction by id or URL: title, description, sale number, departments, location, format, bidding and closing times, sessions with lot ranges, viewing days, saleroom notices, images and lot count.

How to use it

Fetch a Sotheby's auction by the id or url from sothebys/auctions/search or a lot's auction. List its lots with sothebys/auctions/lots.

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)

Response

• @type string (default: "SothebysAuction")
• id string required
• url string nullable
• alias string nullable
• year integer nullable
• description string nullable
• sale_number string nullable
• departments array (default: [])
• state string nullable
• sale_format string nullable
• sale_type string nullable
• currency string nullable
• location string nullable
• timezone string nullable
• conditions_of_sale string nullable
• is_lot_number_hidden boolean nullable
• published_at integer nullable
• bidding_opens_at integer nullable
• closing_starts_at integer nullable
• live_at integer nullable
• closed_at integer nullable
• bidding_phase string nullable
• bidding_method string nullable
• closing_interval integer nullable
• bidding_channels array (default: [])
• phone_bid_cutoff_at integer nullable
• lot_count integer nullable
• images array (default: [])
• sessions array (default: [])
  • @type string (default: "SothebysAuctionSession")
  • id string nullable
  • opens_at integer nullable
  • state string nullable
  • first_lot_number string nullable
  • last_lot_number string nullable
• viewings array (default: [])
  • @type string (default: "SothebysAuctionViewing")
  • location string nullable
  • starts_at integer nullable
  • ends_at integer nullable
• saleroom_notices array (default: [])
  • @type string (default: "SothebysSaleroomNotice")
  • text string nullable
  • lot_id string nullable
  • lot_number string nullable
  • lot_title string nullable
• featured_filters array (default: [])
  • @type string (default: "SothebysFeaturedFilter")
  • name string nullable
  • facet string nullable
  • value string nullable
• ends_at integer nullable
• starts_at integer nullable
• details string nullable
• sale_total number nullable
• sale_total_currency string nullable
• artists array (default: [])
• artist_ids array (default: [])
• brands array (default: [])
• tags array (default: [])
• updated_at integer nullable
• image_caption string nullable
• locations array (default: [])
• divisions array (default: [])
• regions array (default: [])
• latitude number nullable
• longitude 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 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.