/qoo10/products

POST /api/qoo10/products

Price: 10 credits

Get full Qoo10 product details by goodscode (or product URL): name, brand, price, images, rating, review_count, description, seller, shipping options, stock and availability.

How to use it

Fetch a single Qoo10 product by goodscode (numeric id) or a product URL. Returns one item with name, brand, category, image+images, description, rating, review_count, price/list_price/currency/discount_rate, availability, condition, ship_from, seller (alias+name+point_rate) and options (per-inventory stock, ship-from and courier). 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")
• product string required — Qoo10 product goodscode or a product URL containing it (examples: "960300946", "https://www.qoo10.jp/g/960300946"; minLength: 1)

Response

• @type string (default: "Qoo10Product")
• id string required
• url string required
• name string required
• brand string nullable
• brand_id string nullable
• brand_country string nullable
• category string nullable
• image string nullable
• images array (default: [])
• description string nullable
• rating number nullable
• review_count integer nullable
• price number nullable
• list_price number nullable
• currency string (default: "JPY")
• discount_rate number nullable
• availability string nullable
• condition string nullable
• price_valid_until string nullable
• ship_from string nullable
• weight number nullable
• is_coupon_available boolean (default: false)
• is_adult boolean (default: false)
• reward_points integer nullable
• seller object nullable
  • @type string (default: "Qoo10ProductSeller")
  • id string nullable
  • alias string nullable
  • name string nullable
  • point_rate number nullable
• options array (default: [])
  • @type string (default: "Qoo10ProductOption")
  • inventory_no integer (default: 0)
  • stock integer (default: 0)
  • is_sold_out boolean (default: false)
  • ship_from string nullable
  • delivery_fee number (default: 0)
  • guarantee_days integer nullable
  • shipping_center_code string nullable
  • delivery_group_no integer nullable
  • courier string nullable
  • last_mile 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 — Product not found (well-formed but nonexistent goodscode) 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.