/sofmap/stores

POST /api/sofmap/stores

Price: 10 credits

Get the Sofmap (ソフマップ) shop network: every branch with its sub-brands, region and prefecture, postal code and address, map link, opening hours, phone lines and the stock code its second-hand listings refer to.

How to use it

The physical Sofmap branches. Returns the whole network by default, or one branch when store is given as either its id (the url slug, e.g. 'akiba_ekimae') or its numeric code. code is the store_code that the used_products endpoints report for a second-hand unit held in a shop. Each entry also carries name, url, brands (Sofmap, AKIBA, animega, U-FRONT and the other signs sharing the address), region, prefecture, area, postal_code, address, map_url, image, opening_hours, reception_hours, status, phones and twitter_url.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• store string nullable — Return only this store, by its id or its stock code (examples: "akiba_ekimae", "258")
• count integer required — Max number of stores to return (min: 1)

Response

• @type string (default: "SofmapStore")
• id string required
• code string nullable
• name string required
• url string required
• brands array (default: [])
• region string nullable
• prefecture string nullable
• area string nullable
• postal_code string nullable
• address string nullable
• map_url string nullable
• image string nullable
• opening_hours string nullable
• reception_hours string nullable
• status string nullable
• phones array (default: [])
  • @type string (default: "SofmapStorePhone")
  • number string required
  • label string nullable
• twitter_url 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 — 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.