/biccamera/stores

POST /api/biccamera/stores

Price: 5 credits

Get one Bic Camera (ビックカメラ) store by its store code: name, postal code, address, opening hours, storefront and floor-guide images, nearest stations with their train lines, parking, in-store services, contact numbers and social accounts.

How to use it

Fetch one Bic Camera store by its code ('shop007' or just '007'; codes come from the stores search endpoint). Returns name, postal_code, address, opening_hours, image, map_url (Google Maps), floor_guide_image, access (nearest stations and the lines serving them), parking, services, phones (each with the desk name and its opening hours) and social_urls.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• store string required — Bic Camera store code, e.g. 'shop007' or '007' (examples: "shop007")

Response

• @type string (default: "BiccameraStore")
• id string required
• url string required
• name string required
• postal_code string nullable
• address string nullable
• opening_hours string nullable
• image string nullable
• map_url string nullable
• floor_guide_image string nullable
• access array (default: [])
  • @type string (default: "BiccameraStoreAccess")
  • station string required
  • lines array (default: [])
• parking array (default: [])
• services array (default: [])
• phones array (default: [])
  • @type string (default: "BiccameraStorePhone")
  • name string required
  • phone string required
  • hours string nullable
• social_urls array (default: [])

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 store page) 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.