/qoo10/sellers

POST /api/qoo10/sellers

Price: 5 credits

Get Qoo10 seller (shop) details by shop alias (or shop URL): name, logo, satisfaction rate, follower count, item count and coupon availability.

How to use it

Fetch a single Qoo10 seller (mini-shop) by shop alias or shop URL. Returns one item with id, alias, url, name, image (logo), banner, description, satisfaction_rate, is_power_seller, follower_count, item_count and is_coupon_available. Use the domain field for non-Japan marketplaces.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• domain string — Qoo10 marketplace domain. (default: "qoo10.jp"; one of: "qoo10.jp", "qoo10.sg", "qoo10.com.hk", "qoo10.my")
• seller string required — Qoo10 shop alias or a shop URL containing it (examples: "BnD_official", "https://www.qoo10.jp/shop/BnD_official"; minLength: 1)

Response

• @type string (default: "Qoo10Seller")
• id string nullable
• alias string required
• url string required
• name string required
• image string nullable
• banner string nullable
• description string nullable
• satisfaction_rate number nullable
• is_power_seller boolean (default: false)
• follower_count integer nullable
• item_count integer nullable
• is_coupon_available boolean (default: false)

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 not found (nonexistent shop alias) 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.