/joshin/stores

POST /api/joshin/stores

Price: 5 credits

Get one Joshin (上新電機) shop by its store code: name, address, postal code, phone, coordinates, opening state and date, Google place id, shop notices, the services and product ranges the shop offers, its announcements, weekly opening hours, exceptional closures and the nearest sibling shops with their distance.

How to use it

Fetch one joshin shop by its store code ('1916' or a full store page URL; codes come from the stores search endpoint). Returns id, url, name, name_kana, prefecture, city, address, postal_code, phone, latitude, longitude, business_status, opening_date, place_id, notes (shop notices such as an extra counter phone number), services (the product ranges and counters this shop offers, in Japanese, e.g. 模型(鉄道模型), 免税店, 車いす貸出し, ネットで注文　店舗受け取り), announcements (free-text notices the shop publishes, such as an opening notice), business_hours (one entry per weekday with open_time and close_time), special_hours (dated exceptions, is_closed marking a full closure) and nearby_stores with distance_km.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• store string required — Joshin store code, or a full store page URL (examples: "1916", "https://store.joshin.co.jp/detail/1916/"; minLength: 1)

Response

• @type string (default: "JoshinStoreDetail")
• id string required
• url string required
• name string required
• name_kana string nullable
• prefecture string nullable
• city string nullable
• address string nullable
• postal_code string nullable
• phone string nullable
• latitude number nullable
• longitude number nullable
• business_status string nullable
• opening_date string nullable
• notes array (default: [])
• business_hours array (default: [])
  • @type string (default: "JoshinStoreHours")
  • day string required
  • open_time string nullable
  • close_time string nullable
• special_hours array (default: [])
  • @type string (default: "JoshinStoreSpecialHours")
  • start_date string required
  • end_date string nullable
  • open_time string nullable
  • close_time string nullable
  • is_closed boolean (default: false)
• place_id string nullable
• services array (default: [])
• announcements array (default: [])
• nearby_stores array (default: [])
  • @type string (default: "JoshinNearbyStore")
  • id string required
  • url string required
  • name string required
  • address string nullable
  • business_status string nullable
  • distance_km number 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 — Store not found (well-formed store code but no such Joshin shop) 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.