# /sofmap/used_products/search `POST /api/sofmap/used_products/search` Price: 20 credits Search the second-hand catalogue of Sofmap's リコレ！ (Recore) store by keyword and/or category, narrowed by condition grade, maker, price range, warehouse versus shop stock, how many copies of a model are held and the category-specific specification facets, with five orderings. Returns one card per model with its JAN, photo, price range across the copies in stock, condition grade and how many copies are held. ## How to use it Search used.sofmap.com (リコレ！), the second-hand catalogue of Sofmap. This is a different catalogue from the sofmap.com products endpoints and is addressed by JAN code. Give a keyword, a category (e.g. 'pc', 'iphone', 'cam') or both, and narrow with subcategory slugs, used_rank, maker, price_min/price_max, stock_type, stock_count and specs (category-specific facets such as cpu, os or storage_size, whose ids and accepted values come from the used_products/categories endpoint, including the ones published only on a subcategory). The maker names and the price bands this catalogue holds for a scope come from the used_products/facets endpoint. Each card is one model: id is the JAN to pass to the used_products endpoint to list its individual copies, unit_count says how many copies are in stock, and price/price_max span them. Cards also carry name, short_name, model_name, maker, image, used_rank with used_rank_description, accessories, condition_note, missing_parts, spec_highlights, stock_type, store_code and the listed_at/price_reduced_at/released_at unix timestamps. Japanese keywords are supported. All prices are in JPY and tax-included. ## Parameters - `access-token` (string, required) ## Request body - `timeout` (integer) — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500) - `keyword` (string, nullable) — Free-text query (minLength: 1) - `category` (string, nullable) — Top-level category of the second-hand catalogue (one of: "pc", "gaming", "smp", "tab", "wtc", "mac", "iphone", "ipad", "surface", "video", "cam", "dslr", "lens", "headphone", "audio", "visual", "rec-visual", "device", "parts", "game", "kaden-life", "kaden-light", "kaden-joho", "kaden-season", "kaden-kitchen1", "kaden-kitchen2", "kaden-appearance", "kaden-beauty") - `subcategory` (array, nullable) — Second-level category slugs (from the used_products/categories endpoint) (examples: ["note","desktop"]) - `used_rank` (array, nullable) — Condition grades to keep: S unused, A mint, B good, C fair, D faulty, E junk (one of: "S", "A", "B", "C", "D", "E") - `maker` (array, nullable) — Maker names, as published by the used_products/facets endpoint (examples: ["NEC(エヌイーシー)"]) - `stock_type` (string, nullable) — Keep only warehouse stock or only shop stock (one of: "warehouse", "store") - `stock_count` (string, nullable) — Keep only models held in this many copies (one of: "up_to_5", "5_to_9", "10_to_19", "20_or_more") - `specs` (object, nullable) — Category-specific specification filters, keyed by the facet id of the used_products/categories endpoint (examples: {"cpu":["Core i7"],"storage_type_1":["SSD"]}) - `*` (array) - `count` (integer, required) — Max number of results to return (min: 1) - `price_min` (integer, nullable) — Minimum tax-included price in JPY (min: 0) - `price_max` (integer, nullable) — Maximum tax-included price in JPY (min: 0) - `sort` (string) — Result ordering (default: "newest_arrival"; one of: "newest_arrival", "release_date_desc", "release_date_asc", "price_asc", "price_desc") ## Response ### 200 — Successful Response - `@type` (string) (default: "SofmapUsedProductCard") - `id` (string, required) - `jan` (string, nullable) - `url` (string, required) - `name` (string, nullable) - `short_name` (string, nullable) - `model_name` (string, nullable) - `maker` (string, nullable) - `image` (string, nullable) - `price` (number, nullable) - `price_max` (number, nullable) - `price_without_tax` (number, nullable) - `price_without_tax_max` (number, nullable) - `currency` (string) (default: "JPY") - `used_rank` (string, nullable) (one of: "S", "A", "B", "C", "D", "E") - `used_rank_description` (string, nullable) - `unit_count` (integer, nullable) - `accessories` (string, nullable) - `accessories_note` (string, nullable) - `condition_note` (string, nullable) - `missing_parts` (string, nullable) - `spec_highlights` (string, nullable) - `stock_type` (string, nullable) (one of: "warehouse", "store") - `store_code` (string, nullable) - `is_new_arrival` (boolean) (default: false) - `is_price_reduced` (boolean) (default: false) - `listed_at` (integer, nullable) - `price_reduced_at` (integer, nullable) - `released_at` (integer, nullable) ## Errors ### 422 — Validation Error An unknown subcategory slug or specification facet id was given What to do: Check the fields against this schema. A URN with the wrong prefix is the most common cause. - `detail` (array) - `loc` (array, required) - `msg` (string, required) - `type` (string, required) - `input` (any) - `ctx` (object) ### 408 The request ran past its time limit What to do: 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 What to do: 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 What to do: 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 What to do: 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 What to do: Wait at least 30 seconds, then retry. ## Response envelope Success: Array of objects (may be empty if no results) Error: Error may coexist with partial results if it occurs mid-execution. Check X-Error header and status code. Every response carries these 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.