POST /api/backmarket/sellers
Price: 1 credit
Get a Back Market seller by id or seller page URL: company and legal name, description, address, VAT and SIRET numbers, cover image and the average rating over its reviews.
One Back Market refurbished-electronics seller. Takes the seller uuid, the numeric seller id shown in product results (seller_id) or a seller page URL; use the locale of the marketplace the seller sells in.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)locale string — Marketplace region. Determines the catalog, currency and language. (default: "en-us"; one of: "en-us", "es-us", "en-gb", "fr-fr", "de-de", "de-at", "fr-be", "es-es", "it-it", "pt-pt", "nl-nl", "en-ie", "sv-se", "fi-fi", "el-gr", "sk-sk", "ja-jp", "en-au")seller string required — Seller id (uuid), numeric seller id, or a seller page URL (examples: "5f7368c5-9a0d-42d1-8496-7fdbdaa42090", "1720", "https://www.backmarket.com/en-us/s/verizon/5f7368c5-9a0d-42d1-8496-7fdbdaa42090"; minLength: 1)@type string (default: "BackmarketSeller")id string requiredmerchant_id string nullablename string nullablelegal_name string nullablealias string nullableurl string nullabledescription string nullableaddress object nullable@type string (default: "BackmarketSellerAddress")street string nullablestreet2 string nullablecity string nullablepostal_code string nullablestate string nullablecountry_code string nullablecountry string nullablecountry_code string nullablevat_number string nullablesiret_number string nullablecover string nullablerating number nullablerating_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 seller exists with this id in this marketplace region 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.