/liquidation_com/sellers

POST /api/liquidation_com/sellers

Price: 20 credits

Get a Liquidation.com seller by account alias or name: how long they have sold on the site, lifetime and 90-day completed transaction brackets, cancelled-transaction and honored-dispute rates, average days to ship, and the star score for each.

How to use it

Vet a seller before bidding on their lots. Pass seller.alias of a liquidation_com/lots record to get that exact account; several accounts can share one display name. The seller is published only while it has an open lot.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• seller string required — Seller account alias, seller name or seller search URL (examples: "IZZYSALES", "TitanReturns1", "https://www.liquidation.com/auction/search?flag=new&cmd=keyword&searchparam_username_seller=IZZYSALES"; minLength: 1; maxLength: 300)

Response

• @type string (default: "LiquidationComSellerRating")
• id string nullable
• alias string nullable
• name string required
• url string nullable
• is_marketplace_seller boolean required
• selling_since_date string nullable
• lifetime_completed_transactions string nullable
• recent_completed_transactions string nullable
• cancelled_transactions_percent number nullable
• cancelled_transactions_stars integer nullable
• average_days_to_ship number nullable
• shipping_time_stars integer nullable
• honored_disputes_percent number nullable
• honored_disputes_stars integer 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 — No seller with this alias or name has an open lot on Liquidation.com 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.