Rakuten Ichiba shop

GET https://api.api.sh/rakuten/v1/shop
1 credit / call e-commerce try it in the playground →

One Rakuten Ichiba shop: its name, description, shop rating and review count, logo and links, the genres it sells in (with item counts; with genre, that genre's subgenres), and its items (same fields as search, about 45 per page), optionally narrowed by keywords, genre and price. Pass next_page back as page; it is null on the last page.

Every response includes credits_used: the credits this call cost.

Parameters

nametypedescription
shop string Shop code, as in www.rakuten.co.jp/<shop>/. Required unless url or shop_id is given. Example: rakuten24
url string A www.rakuten.co.jp/<shop>/ shop link or an item.rakuten.co.jp/<shop>/... item link.
shop_id integer Numeric shop id (shop.id in responses), instead of shop.
q string Keywords to search within the shop.
genre integer A genre id from genres.
page integer Page number. Pass next_page from the previous response; next_page is null on the last page.
sort standard | price_asc | price_desc | newest | reviews | rating | price_shipping_asc | price_shipping_desc price_shipping_asc / price_shipping_desc: by price including shipping; reviews: most reviewed; rating: best rated.
min_price integer Lowest price, whole yen.
max_price integer Highest price, whole yen.

Every endpoint also takes fresh, raw, fields (see lean responses and caching).

Example

curl "https://api.api.sh/rakuten/v1/shop?shop=rakuten24" \
  -H "x-api-key: $APISH_KEY"

Response

A JSON object with the fields described above, plus raw (the source's own data), cached, fetched_at and credits_used. Errors return {"success": false, "error": "…"} with the HTTP status (see errors). A lookup that ran but found nothing (404) costs the price above; refused calls and errors on our side are free (what's charged).

The fastest way to see the full response is the playground: it runs this endpoint with your account and shows the exact JSON.