Skip to content

Rakuten Scraper API for Product and Seller Data

Rakuten product pages carry a lot of useful marketplace signal: SKU, brand, price, ratings, review count, seller, point rewards, shipping options and the image gallery.

OUTPUT FORMATSHTMLJSONMarkdown

This page explains how a managed scraping API returns those fields from a Rakuten URL, how request options change the result and the credit cost, and where the limits sit.

What the API does with a Rakuten URL

You send a Rakuten product URL and an API key. The service renders the page in a real browser, rotates the outbound IP, and returns the response your scraper can act on. JavaScript rendering, proxy rotation and bot-detection handling are part of the request rather than something you build and maintain.

That matters because Rakuten pages are not static HTML. Prices, stock state, seller blocks and point rewards can be rendered client-side. A plain HTTP fetch often returns a shell; a browser-rendered fetch returns the product record. The API is aimed at teams that want the data without running a headless-browser fleet.

A typical first request is a single call: URL in, HTML or structured JSON out. From there you add options only when the page needs them.

Fields you can expect from a Rakuten product page

The product record the API is built to return covers the commercial facts a merchandising or pricing team usually needs. Use this field map to decide what to store and what to re-check on each run.

  • SKU and brand — the stable identifiers for matching a product across runs.
  • Price — the listed price at fetch time; store the timestamp alongside it.
  • Ratings and review count — useful for seller and product quality signals.
  • Seller — the merchant behind the listing, which matters when vetting vendors.
  • Stock state — whether the item is available at the moment of the request.
  • Point rewards — Rakuten's loyalty points attached to the listing.
  • Shipping options — delivery choices shown on the page.
  • Image gallery — the full set of product images.

These fields are what the page renders publicly. Anything behind a login is out of scope, and the API is not a substitute for Rakuten's own seller or affiliate APIs where those exist.

Three workflows this fits

Inventory and catalogue management. Pull product details on a schedule so your catalogue reflects current SKUs, brands and stock state. The value is in the diff between runs, not a single snapshot.

Price monitoring. Capture price and point rewards together. A listing that drops price but also drops point rewards may not be a real discount, so store both fields and compare the effective cost.

Seller vetting. Collect seller identity alongside ratings and review counts. That lets you rank or filter vendors on evidence rather than a single star value.

Worked example: a price-monitoring record

Suppose you track one Rakuten listing daily. On day one the API returns a record with the SKU, the listed price, the point reward, the seller and the stock state. On day two you fetch the same URL and get a second record.

Your comparison is then field by field: did the price move, did the point reward move, did the seller change, did stock flip? Because the record includes the image gallery and review count, you can also flag listings where the images or review count changed unexpectedly — a signal that the listing was edited rather than repriced.

What you should not do is treat a single fetch as a verified price. The page is a live marketplace listing; the value is only as good as the timestamp you attach to it.

Request options and what they change

The base call returns the page. The options below change what the renderer does and, in several cases, what the request costs in credits.

  • render_js — executes the page in a browser so client-side content appears. Costs 5 credits per successful request.
  • stealth_proxy — a higher-assurance proxy path for pages that block ordinary requests. Costs 75 credits per request.
  • premium_proxy — premium proxy pool; 10 credits with JS rendering disabled, 25 with it enabled.
  • country_code — routes the request through a chosen country or territory. The service advertises 200+ countries and territories on premium proxies, 40+ on classic proxies.
  • extract_rules — CSS or XPath selectors mapped to field names, returning parsed JSON.
  • ai_extract_rules — a natural-language extraction spec, also returning parsed JSON.
  • js_scenario — clicks, scrolling and custom JavaScript before the scrape.
  • Screenshots — full-page capture of the rendered page.

Credit costs are per successful request and depend on which options are enabled. The pricing table below lists plan-level credit allowances and concurrency; the per-request costs above are the ones that determine how far a plan's credits stretch.

From signup to first Rakuten request

  1. Create an account. You get an API key and 1,000 free credits; no card is required for the free credits.
  2. Pick a client. SDKs are published for Python, Node.js, Go, PHP, Ruby and Java, and plain cURL works. Each Rakuten scrape becomes a single function call.
  3. Send the Rakuten URL with your API key. The renderer executes the page, rotates the IP and returns the response.
  4. Add options only where the page needs them — JavaScript rendering, stealth proxy, country targeting, or extraction rules for structured JSON.

The setup path is deliberately short: the API key and a URL are enough for a first result, and the SDKs exist so you do not hand-roll proxy and browser management.

Decision checklist before you commit

Use this to decide whether a managed API is the right fit for your Rakuten workflow.

  • Do you need the page rendered, or is the data available from an official Rakuten API? If an official API covers your need, prefer it.
  • Is the target content public and post-login-free? If not, stop — the API is for public pages.
  • Have you read Rakuten's terms of service for the pages you plan to fetch? Do that before deploying, not after.
  • Can you estimate requests per day and multiply by the credit cost of the options you need? That tells you which plan tier is realistic.
  • Do you have a place to store timestamps alongside prices and stock? Without them the data is not auditable.
  • Do you need structured JSON, or is raw HTML enough? Extraction rules add a step but remove parsing work on your side.

Telling apart the three failure modes

Not every empty result means the same thing, and the fix differs.

Bot block. The page returns a challenge or a stripped shell. The fix is a stronger proxy path or JavaScript rendering, not a selector change.

Missing field. The page rendered but a field you expected is absent. That is usually a listing that does not show that field — for example a product without point rewards — rather than a scraping failure. Check the rendered page before changing extraction rules.

Legal or access limit. The content is behind a login, or Rakuten's terms do not permit the fetch you planned. No request option fixes this; the answer is to change the plan or stop.

Plans and credit allowances

The pricing table below is the captured plan structure: monthly price, API credits, concurrent requests, and which features are included at each tier. JavaScript rendering, rotating and premium proxies, geotargeting, and screenshots and extraction rules are included from the Hobby tier upward. Priority email support, a dedicated account manager and team management appear from the Business tier upward.

API credits are valid for one month and do not roll over. Requests start at 1 credit each, and the per-request costs for JavaScript rendering, premium proxies and stealth proxy are listed in the request-options section above. All prices are exclusive of VAT.

Treat the figures as a dated reference and confirm current pricing before you commit to a tier.

Compliance and data handling

Public-facing pages can usually be scraped, but the target site's terms of service should be reviewed before deployment, and post-login content should be avoided. The service states that it does not collect or store personal data from scraped sites unless the user explicitly requests it.

For Rakuten specifically, product pages are public; seller dashboards, order history and account pages are not. Keep the scope on public product and listing pages.

Captured plan structure: monthly price, credits and concurrency
PlanPrice / monthAPI creditsConcurrent requestsPriority supportAccount managerTeam management
Hobby$1975,00025Not includedNot includedNot included
Freelance$49250,00050Not includedNot includedNot included
Startup (Recommended)$991,000,000100Not includedNot includedNot included
Business$2493,000,000200IncludedIncludedIncluded
Business +$5998,000,000400IncludedIncludedIncluded
Enterprise 14$99914,000,000500IncludedIncludedIncluded
Enterprise 24$1,59924,000,000600IncludedIncludedIncluded
Enterprise 41 (Recommended)$2,39941,000,000700IncludedIncludedIncluded
Enterprise 69$3,59969,000,000800IncludedIncludedIncluded
Enterprise 120$5,799120,000,000900IncludedIncludedIncluded

Captured plan structure; all prices exclusive of VAT. API credits are valid for one month and do not roll over. Confirm current pricing before committing.

Per-request credit costs by option
OptionCredit cost per successful request
Base request1 credit
JavaScript rendering (render_js)5 credits
Premium proxy, JS rendering disabled10 credits
Premium proxy, JS rendering enabled25 credits
Stealth proxy (stealth_proxy)75 credits

Per-request costs are per successful request and depend on which options are enabled.

Frequently asked questions

Do I need a Rakuten account to use the scraper?

No. You sign up for an API key, get 1,000 free credits without a card, and send the URL. The scraper works on public pages; post-login content is out of scope.

Is scraping Rakuten legal?

Public-facing pages can usually be scraped, but you should review Rakuten's terms of service before deploying and avoid post-login content. The answer depends on your jurisdiction and your use of the data, not on the tool alone.

What data can I extract from Rakuten?

Anything that renders on the public page. For product pages that typically means SKU, brand, price, ratings, review count, seller, point rewards, shipping options and the image gallery. Use extract_rules with CSS selectors or ai_extract_rules for AI-driven extraction to get structured JSON back.

How do I get structured JSON from Rakuten?

You have two routes to a parsed JSON response. With extract_rules, you supply CSS selectors and pair each one with the field name you want it stored under. With ai_extract_rules, you describe the fields you want in plain language instead of writing selectors. Either way, the API returns the result already parsed as JSON, so no HTML parsing is needed on your side.

Which programming languages can I use?

Any. SDKs are published for Python, Node.js, Go, PHP, Ruby and Java, and plain cURL works. Pick whatever your stack already uses.

How much does it cost to scrape Rakuten?

There are 1,000 free credits on signup with no card required. Paid plans start at $19/month for higher volume and concurrency. Credit cost per request depends on options: 5 credits for JavaScript rendering, 25 for premium proxy with JS, 75 for stealth proxy. Confirm current pricing before committing.