POST /api/liveauctioneers/catalogs/search
Price: 20 credits
Search the LiveAuctioneers auction calendar of upcoming and running auctions by day, auction format, country, auction house and shipping option. Returns catalogs with title, status, sale start, lot count, currency, buyer's premium tiers, payment options, sale address, cover lots and the auction house.
Browse upcoming and running auctions; for one house's past auctions use liveauctioneers/auctioneers/auctions. Pass a result's id to liveauctioneers/catalogs/lots for its lots.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)sale_date string nullable — Day on which the auction runs (format: date; examples: "2026-09-28")sale_type string nullable — Auction format (one of: "live_auction", "timed_auction", "timed_plus_auction", "buy_now", "catalog_only")country string nullable — Country where the auction takes place, by English name (examples: "United Kingdom"; minLength: 2)auction_house_id string nullable — Only auctions of this auction house (examples: "9391"; minLength: 1)excluded_auction_house_ids array — Leave out auctions of these auction houses (default: []; examples: ["9391"])shipping string nullable — Shipping option the auction offers (one of: "live_shipping", "free_local_pickup", "in_house_shipping", "flat_rate_shipping", "free_shipping")count integer required — Max number of auctions to return (min: 1)@type string (default: "LiveAuctioneersCatalog")id string requiredurl string nullablestatus string nullabledescription string nullablepreview string nullablelot_count integer nullableabsentee_bidder_count integer nullablecurrency string nullablecurrency_symbol string nullablesale_start_at integer nullablesale_end_at integer nullablesale_end_estimated_at integer nullablepublished_at integer nullableis_timed boolean nullableis_timed_plus boolean nullableis_catalog_only boolean nullablehas_video boolean nullablehas_explicit_material boolean nullableis_autopay boolean nullableis_instant_autopay boolean nullableis_escrow_supported boolean nullableaccepts_ach boolean nullableaccepts_online_payment boolean nullableis_ach_required boolean nullablebuyers_premium object nullable@type string (default: "LiveAuctioneersBuyersPremium")low_percent number nullablelow_cutoff number nullablemiddle_percent number nullablemiddle_cutoff number nullablehigh_percent number nullablepayment_options array (default: [])shipping_options array (default: [])ships_to string nullableaddress object nullable@type string (default: "LiveAuctioneersAddress")address string nullableaddress2 string nullablecity string nullablestate string nullablepostal_code string nullablecountry_code string nullablecountry string nullablelatitude number nullablelongitude number nullableseller_id string nullableseller object nullable@type string (default: "LiveAuctioneersSellerSummary")id string requiredname string nullablealias string nullableurl string nullableimage string nullableaddress string nullableaddress2 string nullablecity string nullablestate_code string nullablestate string nullablepostal_code string nullablecountry_code string nullablecountry string nullablecover_lots array (default: [])@type string (default: "LiveAuctioneersCoverLot")id string requiredimage string nullablebid_increments array (default: [])@type string (default: "LiveAuctioneersBidIncrement")from_amount number requiredincrement number nullable422 — 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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.