/lohaco/products/ranking

POST /api/lohaco/products/ranking

Price: 10 credits

Get the daily LOHACO (ロハコ) bestseller ranking, site-wide or for one category: rank, product, price, unit price, stock, rating, review count and the date the ranking was refreshed.

How to use it

Daily bestseller ranking of LOHACO (ロハコ). Omit `category` for the site-wide chart, or pass a category id from lohaco/categories for that section's chart. The chart holds 20 positions and is refreshed once a day — `updated_date` carries the refresh date as shown on the site. Drop-shipped items sit under a different `store_id`; pass `store_id/id` to lohaco/products to fetch them 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)
• count integer required — Max number of ranked products to return (min: 1; max: 20)
• category string nullable — Category id to rank within; omit for the site-wide ranking (examples: "51006")

Response

• @type string (default: "LohacoRankingItem")
• rank integer required
• id string required
• url string required
• store_id string required
• name string required
• image string nullable
• price number nullable
• unit_price number nullable
• currency string (default: "JPY")
• in_stock boolean nullable
• rating number nullable
• review_count integer nullable
• is_set_discount boolean nullable
• point_percent number nullable
• ranking_name string nullable
• updated_date 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 — Category not found (well-formed id but no such category 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.