/invaluable/lots/price_results

POST /api/invaluable/lots/price_results

Price: 20 credits

Search past Invaluable auction lots with their realized sold prices, by keyword, category, seller country, currency, auction house, artist, sold price and auction date, newest, oldest or by price. Each lot carries its sold price, estimate, auction date, auction house and category.

How to use it

Use for realized prices and comparables; sold_price is empty on a lot that did not sell or whose result was not published, and min_price=1 keeps only lots with a price.

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: "tiffany lamp"; minLength: 1)
• category string nullable — Top-level category (one of: "Asian Art & Antiques", "Automobiles, Boats & Airplanes", "Collectibles", "Commercial & Industrial", "Decorative Art", "Dolls, Bears & Toys", "Farm & Agriculture", "Fine Art", "Firearms", "Furniture", "Heavy Equipment", "Jewelry", "Wines & Spirits")
• subcategory string nullable — Category within the chosen top-level category (examples: "Ceramics & Pottery"; minLength: 1)
• countries array — Countries of the selling auction house (default: []; one of: "Argentina", "Australia", "Austria", "Belgium", "Brazil", "Bulgaria", "Canada", "China", "Colombia", "Croatia, Republic of (Hrvatska)", "Cyprus", "Czech Republic", "Denmark", "Egypt", "Estonia", "Ethiopia", "Finland", "France", "Germany", "Greece", "Hong Kong", "Hungary", "India", "Indonesia", "Ireland", "Israel", "Italy", "Japan", "Kenya", "Korea, South (Republic)", "Latvia", "Lebanon", "Liechtenstein", "Lithuania", "Luxembourg", "Malaysia", "Malta", "Mexico", "Monaco", "Morocco", "Netherlands", "New Zealand", "Nigeria", "Norway", "Pakistan", "Philippines", "Poland", "Portugal", "Qatar", "Romania", "San Marino", "Serbia", "Singapore", "South Africa", "Spain", "Sweden", "Switzerland", "Taiwan", "Thailand", "Turkey", "Ukraine", "United Arab Emirates", "United Kingdom", "United States of America", "Uruguay", "Venezuela", "Viet Nam"; examples: ["Germany"])
• currencies array — Lot currencies (default: []; one of: "AUD", "CAD", "CHF", "CZK", "DKK", "EUR", "GBP", "HKD", "HUF", "JPY", "MYR", "PHP", "PLN", "SGD", "THB", "USD", "ZAR"; examples: ["EUR"])
• auction_house string nullable — Auction house id or URL (examples: "8RA3GB6FWF", "https://www.invaluable.com/auction-house/abell-auction-8ra3gb6fwf/"; minLength: 1)
• artist string nullable — Artist id or URL (examples: "EU429SACMA", "https://www.invaluable.com/artist/haring-keith-eu429sacma/"; minLength: 1)
• has_image boolean nullable — true keeps lots with a photo, false lots without
• date_from string nullable — Earliest auction date (format: date; examples: "2025-01-01")
• date_to string nullable — Latest auction date (format: date; examples: "2025-12-31")
• sort string — Result order (default: "newest"; one of: "newest", "oldest", "price_desc", "price_asc")
• min_price number nullable — Lowest sold price, in the lot's currency (min: 0)
• max_price number nullable — Highest sold price, in the lot's currency (min: 0)
• count integer required — Max number of results (min: 1; max: 20000)

Response

• @type string (default: "InvaluableLotSummary")
• id string required
• numeric_id string nullable
• url string nullable
• lot_number string nullable
• description string nullable
• details string nullable
• image string nullable
• image_width integer nullable
• image_height integer nullable
• estimate_low number nullable
• estimate_high number nullable
• current_bid number nullable
• reserve_price number nullable
• sold_price number nullable
• bid_count integer nullable
• currency string nullable
• currency_symbol string nullable
• sale_type string nullable
• sale_at integer nullable
• sale_local_time string nullable
• ends_at integer nullable
• listed_at integer nullable
• is_closed boolean nullable
• is_featured boolean nullable
• is_parity boolean nullable
• is_results_posted boolean nullable
• favorite_count integer nullable
• activity_count integer nullable
• supercategory string nullable
• supercategory_id string nullable
• category string nullable
• category_id string nullable
• subcategory string nullable
• subcategory_id string nullable
• category_paths array (default: [])
• house_category string nullable
• house_category_id string nullable
• house_category_path string nullable
• location string nullable
• state string nullable
• country string nullable
• latitude number nullable
• longitude number nullable
• auction_id string nullable
• auction_house_id string nullable
• auction_house_name string nullable
• artist_id string nullable
• artist_name 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.