POST /api/liveauctioneers/auctioneers
Price: 1 credit
Get one LiveAuctioneers auction house by id or URL: name, address, logo, description, website, email, phone, follower count, upcoming, live and past auction counts, top-rated status and the review rating with its accuracy, payment, responsiveness and shipping scores and star histogram.
Fetch an auction house by its numeric id or /auctioneer/ URL. Use liveauctioneers/auctioneers/auctions for its catalogs, and liveauctioneers/auctioneers/directory to find an id by name.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)auctioneer string required — LiveAuctioneers auction house id or auctioneer page URL (examples: "1998", "https://www.liveauctioneers.com/auctioneer/1998/williams-auctions-llc/"; minLength: 1)@type string (default: "LiveAuctioneersAuctioneer")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 nullabledescription string nullablewebsite_url string nullableemail string nullablephone string nullablefollower_count integer nullableupcoming_auction_count integer nullablelive_auction_count integer nullablepast_auction_count integer nullableis_top_rated boolean nullableaccepts_public_reviews boolean nullablerating object nullable@type string (default: "LiveAuctioneersRating")overall number nullableaccuracy number nullablepayment number nullableresponsiveness number nullableshipping number nullablereview_count integer nullablefive_star_count integer nullablefour_star_count integer nullablethree_star_count integer nullabletwo_star_count integer nullableone_star_count integer 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 LiveAuctioneers auction house 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.