/ssg/sellers

POST /api/ssg/sellers

Price: 10 credits

Get an SSG.COM seller store by id or URL: name, tagline, vendor ids, seller grade, category sales ranking, rating, average shipping days, question answer rate, followers, product count, best keywords and categories

How to use it

Takes the store id of a seller home URL (www.ssg.com/sellerhome/<id>/main.ssg), for example 210890. Vendor ids and store numbers returned elsewhere are not seller store ids and answer 412.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• seller string required — SSG seller store id or URL (examples: "210890", "https://www.ssg.com/sellerhome/210890/main.ssg")

Response

• @type string (default: "SsgSellerStore")
• id string required
• url string required
• name string nullable
• tagline string nullable
• image string nullable
• vendor_id string nullable
• parent_vendor_id string nullable
• vendor_type_code string nullable
• rating number nullable
• average_shipping_days number nullable
• question_answer_rate number nullable
• follower_count integer nullable
• best_keywords array (default: [])
• categories array (default: [])
  • @type string (default: "SsgSellerCategory")
  • id string nullable
  • name string nullable
• grade string nullable
• grade_key string nullable
• best_seller_title string nullable
• category_sales_ranking array (default: [])
  • @type string (default: "SsgSellerRanking")
  • category_name string nullable
  • rank integer nullable
• product_count integer nullable
• title_image 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 — SSG has no seller store under that 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.

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.