/sothebys/lots

POST /api/sothebys/lots

Price: 5 credits

Get one Sotheby's auction lot by id or URL: title, artist, catalogue description, provenance, literature, exhibition history, condition, estimate, bidding state, images, the realized sale price where Sotheby's publishes it, and the auction it belongs to.

How to use it

Fetch a Sotheby's lot by the id or url from sothebys/lots/search, sothebys/auctions/lots or sothebys/artists/lots. sale_price is the realized price and sold_status the outcome for past lots.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• lot string required — Sotheby's lot id or lot URL (examples: "9644ed0b-0d41-4fe7-9c19-60c42afa29d6", "https://www.sothebys.com/en/buy/auction/2020/picasso-prints-ceramics/taureau-alain-ramie-255", "00000164-6444-d1db-a5e6-ed67d3c70000"; minLength: 1)

Response

• @type string (default: "SothebysLot")
• id string required
• url string nullable
• alias string nullable
• lot_number string nullable
• subtitle string nullable
• creators string nullable
• designation string nullable
• description string nullable
• catalogue_note string nullable
• provenance string nullable
• literature string nullable
• exhibition string nullable
• saleroom_notice string nullable
• notices array (default: [])
• condition_state string nullable
• condition_report string nullable
• condition_disclaimer string nullable
• condition_contact_email string nullable
• video_url string nullable
• languages array (default: [])
• tags array (default: [])
• symbols array (default: [])
  • @type string (default: "SothebysLotSymbol")
  • id string nullable
  • name string nullable
  • description string nullable
  • former_name string nullable
• images array (default: [])
• parcel_name string nullable
• parcel_lot_count integer nullable
• is_premium boolean nullable
• is_crypto_accepted boolean nullable
• withdrawn_state string nullable
• sale_number string nullable
• session_id string nullable
• session_opens_at integer nullable
• session_state string 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
• next_bid number 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
• ends_at integer nullable
• previous_lot_id string nullable
• next_lot_id string nullable
• auction object nullable
  • @type string (default: "SothebysLotAuction")
  • id string nullable
  • url string nullable
  • alias string nullable
  • year integer nullable
  • sale_number string nullable
  • currency string nullable
  • departments array (default: [])
  • state string nullable
  • sale_format string nullable
  • sale_type string nullable
  • location string nullable
  • published_at integer nullable
  • bidding_opens_at integer nullable
  • closing_starts_at integer nullable
  • live_at integer nullable
  • closed_at 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 — No Sotheby's lot 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.