/newegg/sellers

POST /api/newegg/sellers

Price: 5 credits

Get a Newegg marketplace seller store by store key (or store URL): seller name, store name, alias, rating, review_count, positive feedback rate, top-rated/hot-seller flags, follower count, legal name, logo and store location.

How to use it

Fetch a single Newegg marketplace seller store by its store key (e.g. Techjunkie, the alias returned as seller.alias from newegg/products) or a full seller store URL. Returns one store with id, name, store_name, alias, rating (and rating_last_12m), review_count (and review_count_last_12m), positive_rate (and positive_rate_last_12m), is_top_rated, is_hot_seller, follower_count, legal_name, description, image and store location (city/state/country).

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• seller string required — Newegg seller store key or a seller store URL (examples: "Techjunkie", "https://www.newegg.com/Seller-Store/Techjunkie"; minLength: 1)

Response

• @type string (default: "NeweggSellerStore")
• id string nullable
• name string nullable
• alias string nullable
• store_name string nullable
• rating number nullable
• rating_last_12m number nullable
• review_count integer nullable
• review_count_last_12m integer nullable
• positive_rate number nullable
• positive_rate_last_12m number nullable
• is_top_rated boolean nullable
• is_hot_seller boolean nullable
• follower_count integer nullable
• legal_name string nullable
• description string nullable
• image string nullable
• city string nullable
• state string nullable
• country string 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 — Seller store not found (well-formed but nonexistent store key, or page has no seller) 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.