/mercari/items/search

POST /api/mercari/items/search

Price: 1 credit

Search Mercari (jp.mercari.com) items by keyword with optional filters

How to use it

Search Mercari Japan (jp.mercari.com) items by keyword. Supports filters: category_id, sort (score/created_time/price/num_likes), order (desc/asc), status (on_sale/sold_out), price_min, price_max.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• keyword string required — Search keyword (examples: "ps5 本体", "iphone 15"; minLength: 1)
• count integer required — Max number of results to return (min: 1; max: 600)
• category_id integer nullable — Mercari category ID filter (e.g. 76 for game consoles) (examples: 76)
• sort string nullable — Sort field. Default: score (relevance) (one of: "score", "created_time", "price", "num_likes")
• order string nullable — Sort order. Default: desc (one of: "desc", "asc")
• status array nullable — Filter by item status. Empty/None = no filter (one of: "on_sale", "sold_out", "trading")
• price_min integer nullable — Minimum price (JPY) (min: 0)
• price_max integer nullable — Maximum price (JPY) (min: 0)

Response

• @type string (default: "MercariSearchItem")
• id string required
• url string required
• name string required
• price integer (default: 0)
• currency string (default: "JPY")
• status string nullable
• photo string nullable
• thumbnail string nullable
• condition_id integer nullable
• category_id integer nullable
• brand object nullable
  • @type string (default: "MercariSearchItemBrand")
  • id integer required
  • name string required
  • subname string nullable
• seller_id integer nullable
• shop_name string nullable
• shipping_payer_id integer nullable
• shipping_method_id integer nullable
• item_type string nullable
• is_no_price boolean (default: false)
• is_liked boolean (default: false)
• auction object nullable
  • @type string (default: "MercariSearchAuction")
  • end_at integer nullable
  • bid_count integer (default: 0)
  • highest_bid integer (default: 0)
  • initial_price integer (default: 0)
• created_at integer nullable
• updated_at integer 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 — 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.