/qoo10/products/search

POST /api/qoo10/products/search

Price: 10 credits

Search Qoo10 products by keyword with filters for shipping origin, category, brand, price range and special-deal type. Returns id, name, brand, price, image, seller and ship-from.

How to use it

Search Qoo10 products by keyword. Returns results with id (goodscode), url, name, brand, image, price/list_price/currency, reward_points, ship_from, is_coupon_available, is_ad and seller (alias+name+is_power_seller). Filter with sort, ship_from, category, brand, price_min/price_max, discount_type. 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")
• keyword string required — Search keyword (examples: "VT シートマスク", "toner pad"; minLength: 1)
• count integer required — Max number of results to return (min: 1)
• sort string — Result ordering (default: "ranking"; one of: "ranking", "price_asc", "price_desc", "newest", "most_reviewed")
• ship_from string — Filter by shipping origin (default: "all"; one of: "all", "domestic", "korea")
• category string nullable — Filter by category code (gdlc_cd)
• brand string nullable — Filter by brand id (brandno)
• price_min integer nullable — Minimum price in JPY (min: 0)
• price_max integer nullable — Maximum price in JPY (min: 0)
• discount_type string nullable — Filter by special-deal type (one of: "time_sale", "today_deal", "group_buy", "video_shop", "e_ticket")

Response

• @type string (default: "Qoo10SearchProduct")
• id string required
• url string required
• name string nullable
• brand string nullable
• brand_id string nullable
• image string nullable
• image_count integer (default: 0)
• price number nullable
• list_price number nullable
• currency string (default: "JPY")
• reward_points integer nullable
• ship_from string nullable
• is_coupon_available boolean (default: false)
• is_ad boolean (default: false)
• seller object nullable
  • @type string (default: "Qoo10SearchSeller")
  • alias string nullable
  • name string nullable
  • is_power_seller 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 — The entity was not found, or a precondition failed 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.