/sofmap/used_products

POST /api/sofmap/used_products

Price: 20 credits

Get every second-hand unit Sofmap's リコレ！ (Recore) store holds under one JAN code. Each physical unit is returned separately with its own condition grade, price, photo, bundled accessories, cosmetic condition note, missing parts, full specification table and the shop or warehouse holding it.

How to use it

Fetch the second-hand stock of one model on used.sofmap.com (リコレ！) by JAN code. This is a different catalogue from the sofmap.com products endpoint: it is addressed by JAN rather than by product number, and one JAN maps to SEVERAL physical units, so the answer is a list even for a single model and count says how many of them to return, newest listing first. Keep the leading zeros of a JAN, they are part of the key. Each unit carries jan (its own barcode), binding_jan (the model all the units share, and the value to pass back here), id (the sofmap.com product number of that unit, usable with the products endpoint) and product_url, name, short_name, model_name, maker, image, price and price_without_tax in JPY, used_rank (S unused, A mint, B good, C fair, D faulty, E junk) with used_rank_description, accessories and accessories_note, condition_note, missing_parts, spec_highlights, specs, stock_type (warehouse or store), store_code (matching the code of the stores endpoint), is_new_arrival, is_price_reduced, listed_at, price_reduced_at and released_at as unix seconds.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• jan string required — JAN code of the second-hand product, keeping any leading zeros (examples: "2000570353023", "0889349183304")
• count integer required — Max number of units to return (min: 1)

Response

• @type string (default: "SofmapUsedProduct")
• jan string required
• binding_jan string nullable
• id string nullable
• url string required
• product_url string nullable
• name string nullable
• short_name string nullable
• model_name string nullable
• maker string nullable
• image string nullable
• price number nullable
• price_without_tax number nullable
• currency string (default: "JPY")
• used_rank string nullable (one of: "S", "A", "B", "C", "D", "E")
• used_rank_description string nullable
• category_id string nullable
• accessories string nullable
• accessories_note string nullable
• condition_note string nullable
• missing_parts string nullable
• spec_highlights string nullable
• specs object (default: {})
  • * string
• stock_type string nullable (one of: "warehouse", "store")
• store_code string nullable
• stock_count integer 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 — 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 — No second-hand unit is listed under this JAN code on used.sofmap.com 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.