/christies/lots

POST /api/christies/lots

Price: 5 credits

Get one Christie's lot — live auction, online auction or private sale — by id or URL: title, catalogue details, provenance, literature, exhibition history, lot essay, images, dimensions, estimate, realised price or current bid, the sale it belongs to and the specialists handling it.

How to use it

Fetch a single Christie's lot by the id or URL that christies/lots/search, christies/auctions/lots or christies/artists return. A numeric id is a christies.com lot, a sale.lot id such as 24560.13 is an online-only lot.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• lot string required — Christie's lot id or lot URL (examples: "6603770", "24560.13", "https://www.christies.com/en/lot/lot-6603770", "https://onlineonly.christies.com/s/prints-multiples/pablo-picasso-1881-1973-13/323238", "MS00003027-001"; minLength: 1)

Response

• @type string (default: "ChristiesLot")
• id string required
• lot_reference string nullable
• lot_number string nullable
• online_item_id string nullable
• sale_type string nullable
• url string nullable
• subtitle string nullable
• tertiary_title string nullable
• consignment_note string nullable
• details string nullable
• provenance string nullable
• literature string nullable
• exhibited string nullable
• essay string nullable
• essay_url string nullable
• special_notice string nullable
• further_details string nullable
• sections array (default: [])
  • @type string (default: "ChristiesLotSection")
  • text string required
• image string nullable
• images array (default: [])
• media_urls array (default: [])
• dimensions string nullable
• height_cm number nullable
• width_cm number nullable
• currency string nullable
• estimate_low number nullable
• estimate_high number nullable
• estimate_text string nullable
• is_estimate_on_request boolean nullable
• is_price_on_request boolean nullable
• price_realised number nullable
• price_realised_text string nullable
• current_bid number nullable
• current_bid_text string nullable
• bid_count integer nullable
• lot_status string nullable
• is_unsold boolean nullable
• is_withdrawn boolean nullable
• start_at integer nullable
• end_at integer nullable
• registration_close_at integer nullable
• previous_lot_url string nullable
• next_lot_url string nullable
• sale object nullable
  • @type string (default: "ChristiesLotSale")
  • id string nullable
  • number string nullable
  • room_code string nullable
  • location string nullable
  • url string nullable
  • sale_type string nullable
  • start_at integer nullable
  • end_at integer nullable
  • registration_close_at integer nullable
  • time_zone string nullable
  • is_over boolean nullable
  • is_in_progress boolean nullable
• symbols array (default: [])
  • @type string (default: "ChristiesLotSymbol")
  • code string nullable
  • symbol string nullable
  • name string nullable
  • description string nullable
• specialists array (default: [])
  • @type string (default: "ChristiesSpecialist")
  • name string required
  • email string nullable
  • phone string nullable
  • image 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 Christie'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.