/christies/lots/search

POST /api/christies/lots/search

Price: 10 credits

Search Christie's sold lots or lots currently offered, by keyword, category, artist, item type, material, origin, subject, period, size, estimate range and sale kind. Returns lot cards with title, image, estimate, realised price, sale dates and the sale they belong to.

How to use it

Search Christie's lots, sold by default or available with status. Facet filters take the label shown on christies.com, such as Pablo Picasso or Ceramic. 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)
• keyword string nullable — Search text (examples: "picasso"; minLength: 1)
• status string — Sold lots or lots open for sale (default: "sold"; one of: "sold", "available")
• sort string — Result order (default: "relevance"; one of: "relevance", "date", "price_asc", "price_desc")
• sale_kind string nullable — Auction lots or private-sale items (one of: "auction", "private_sale")
• categories array — Object categories (default: []; one of: "Wine, Spirits & Cigars", "Paintings", "All other categories of objects", "Furniture & Lighting", "Jewelry", "Drawings & Watercolors", "Prints & Multiples", "Sculptures, Statues & Figures", "Books & Manuscripts", "Watches", "Handbags, Textiles & Costume", "Photographs", "Ancient Art & Antiquities", "Rugs & Carpets", "Memorabilia", "Posters, Signage & Advertising", "Clocks", "Arms & Armor", "Fossils & Minerals", "Musical Instruments", "Installations & Video Art", "Non-Fungible Token", "Automobiles, Cars, Motorcycles, and Automobilia")
• artists array — Artist, maker or author names (default: []; examples: ["Pablo Picasso"])
• item_types array — Item types (default: []; examples: ["Plate"])
• materials array — Materials or media (default: []; examples: ["Ceramic"])
• origins array — Places of origin (default: []; examples: ["Spain"])
• subject_themes array — Subject matter or themes (default: []; examples: ["Portrait"])
• periods array — Dates or periods of creation (default: []; examples: ["1950s"])
• sizes array — Size or bottle format (default: []; examples: ["Magnum"])
• 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; max: 10000)

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 — The entity was not found, or a precondition failed 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.