/christies/auctions/lots

POST /api/christies/auctions/lots

Price: 20 credits

List the lots of one Christie's auction, live or online, in catalogue order or by estimate, with keyword, artist, category, item type, material, origin, style, period and estimate filters. Returns lot cards with title, image, estimate and realised price.

How to use it

List every lot of a Christie's auction by its sale id or auction URL. Facet filters take the label shown on the auction page, such as Pablo Picasso or Paintings. Pass a result's id to christies/lots for the full lot.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• auction string required — Christie's auction id or auction URL (examples: "31076", "https://www.christies.com/en/auction/auction-31064"; minLength: 1)
• keyword string nullable — Search text within the auction (examples: "kusama"; minLength: 1)
• sort string — Result order (default: "lot_number"; one of: "lot_number", "estimate_asc", "estimate_desc")
• artists array — Artist, maker or author names (default: []; examples: ["Pablo Picasso"])
• categories array — Object categories (default: []; examples: ["Paintings"])
• item_types array — Item types (default: []; examples: ["paintings"])
• materials array — Materials or media (default: []; examples: ["canvas"])
• origins array — Places of origin (default: []; examples: ["China"])
• styles array — Stylistic periods (default: []; examples: ["Contemporary"])
• periods array — Dates or periods of creation (default: []; examples: ["1950s"])
• min_estimate integer nullable — Lowest estimate (min: 0)
• max_estimate integer nullable — Highest estimate (min: 0)
• count integer required — Max number of lots to return (min: 1)

Response

• @type string (default: "ChristiesLotCard")
• id string required
• lot_reference string nullable
• lot_number string nullable
• sale_type string nullable
• url string nullable
• subtitle string nullable
• tertiary_title string nullable
• consignment_note string nullable
• description string nullable
• image string 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
• is_withdrawn boolean nullable
• is_sale_over boolean nullable
• is_sale_in_progress boolean nullable
• start_at integer nullable
• end_at integer nullable
• sale_id string nullable
• sale_number string nullable
• sale_location 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 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.