POST /api/catawiki/sellers/lots
Price: 20 credits
List the lots a Catawiki seller currently has in auction, optionally within one auction type, as lot cards with title, images, auction id, current bid in EUR, USD and GBP, reserve state and bidding end time.
List a Catawiki seller's lots in running auctions by seller id or URL. Narrow to one auction type with an auction_type_id from catawiki/sellers.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)seller string required — Catawiki seller id or seller profile URL (examples: "1575981", "https://www.catawiki.com/en/u/1575981-swissonly"; minLength: 1)auction_type_id string nullable — Auction type id from the seller's auction_types in catawiki/sellers (examples: "507")count integer required — Max number of lots to return (min: 1)@type string (default: "CatawikiLotCard")id string requiredsubtitle string nullableurl string nullableimage string nullablethumbnail string nullableauction_id string nullablefavorite_count integer nullablehas_reserve_price boolean nullablehas_free_shipping boolean nullableis_explicit_content boolean nullablebuy_now_price_eur number nullableseller_name string nullableseller_country_code string nullablebidding_start_at integer nullablebidding_end_at integer nullablecurrent_bid object nullable@type string (default: "CatawikiAmount")eur number nullableusd number nullablegbp number nullableis_reserve_price_met boolean nullableis_closed boolean nullableis_buy_now_available boolean nullablehighest_bidder_token string nullablewinner_token string 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 — No Catawiki seller exists at this id. 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.