/lohaco/products

POST /api/lohaco/products

Price: 10 credits

Get a LOHACO (ロハコ) product by item code or product URL: title, price, unit price, stock, brand, JAN code, maker, full specification table, average rating and review count, category breadcrumbs, promotion tags, images, sibling variants, delivery lead time and PayPay point rate.

How to use it

Get one LOHACO (ロハコ, Japanese consumer e-commerce run by ASKUL) product. `item` accepts the bare item code (e.g. 'u254244'), the `store_id/id` pair from lohaco/products/search, or a full product URL. Prices are JPY including tax. `specs` is the full category-specific specification table (contents, ingredients, origin, packaging…); `variants` lists sibling items that differ along `variant_axis` (container, volume, pack size). Passing `store_id/id` for drop-shipped items answers in one round trip.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• item string required — LOHACO item code, store_alias/item_code or a full product URL (examples: "u254244", "h-lohaco4/hn79062", "https://lohaco.yahoo.co.jp/store/h-lohaco/item/u254244/"; minLength: 1)

Response

• @type string (default: "LohacoProduct")
• id string required
• url string required
• name string required
• image string nullable
• images array (default: [])
• price number nullable
• unit_price number nullable
• discount_rate number nullable
• currency string (default: "JPY")
• in_stock boolean nullable
• availability string nullable
• is_best_price boolean nullable
• is_subscription_available boolean nullable
• brand string nullable
• brand_id string nullable
• maker string nullable
• jan_code string nullable
• headline string nullable
• caption string nullable
• description string nullable
• care_comment string nullable
• rating number nullable
• review_count integer nullable
• category_id string nullable
• product_category_id string nullable
• category string nullable
• breadcrumbs array (default: [])
  • @type string (default: "LohacoBreadcrumb")
  • name string required
  • url string nullable
• tags array (default: [])
• specs object (default: {})
  • * string
• variants array (default: [])
  • @type string (default: "LohacoVariant")
  • id string required
  • url string required
  • store_id string required
  • name string nullable
  • image string nullable
  • price number nullable
  • in_stock boolean nullable
  • options object (default: {})
    • * string
• variant_axis string nullable
• seller_id string nullable
• store_name string nullable
• delivery_lead_time string nullable
• free_shipping_threshold number nullable
• base_postage number nullable
• point_percent number nullable
• category_rank integer nullable
• category_rank_name string nullable
• order_limit 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 — Product not found (well-formed item code but no such product on LOHACO) 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.