Skip to content

Rakuten Books Scraper API: Turn Book Pages Into Structured Data

Rakuten Books pages carry the catalogue details most book-data projects need, but they also sit behind JavaScript rendering and bot checks.

OUTPUT FORMATSHTMLJSONMarkdown

This page explains what a managed scraping API returns from a Rakuten Books URL, how the three common jobs differ, and how credit cost changes with the options you enable.

What comes back from a Rakuten Books URL

The API accepts a public Rakuten Books URL and returns rendered, parsed output rather than raw HTML you have to dissect. The catalogue fields the scraper reads are book title, author, publisher, price, ISBN, publication date, page count and customer ratings. You can receive parsed HTML or structured JSON, and you can also ask for clean Markdown if the downstream consumer is a language model.

A useful way to think about the output is in two layers:

  • Catalogue layer — the fields above, present on standard book pages.
  • Extraction layer — anything else that renders on the public page, pulled with extract_rules (CSS selectors) or ai_extract_rules (natural-language instructions).

If a field is missing from the catalogue layer, the usual cause is that the page does not publish it, not that the API dropped it. Check the live page before filing a bug.

Three job types and what each one needs

Most Rakuten Books scraping work falls into one of three shapes. They share the same request mechanics but differ in what you extract and how you validate the result.

  1. Trending content tags — collect the tags and topic labels that appear on Rakuten Books pages to see which subjects are getting attention. Useful for competitor positioning and editorial planning. Validation: confirm the tag list is non-empty and that tags match the visible page.
  2. Book pricing data — capture price fields across a set of titles or a category. Useful for market comparison and repricing decisions. Validation: spot-check a handful of prices against the live page, and record the capture date, because prices move.
  3. Author biography data — pull author profile text to study which authors are being promoted and how. Useful for publishing and content strategy. Validation: confirm the bio block exists on the page before treating an empty result as an error.

A single request can combine catalogue fields with one of these extraction jobs, so you rarely need separate pipelines per job type.

Field and control map

The table below pairs each reader goal with the request control that serves it and the output you should expect. It is a planning aid, not a schema — the exact request and response contract lives in the API documentation.

GoalControl to setOutput to expect
Render a JavaScript-heavy book pagerender_jsFully rendered HTML or JSON
Get past aggressive bot checksstealth_proxyPage content instead of a block page
Target a specific storefront regioncountry_codeRegion-appropriate page content
Pull named fields with selectorsextract_rulesStructured JSON keyed by your selectors
Pull fields described in plain languageai_extract_rulesStructured JSON from an AI extraction pass
Capture a visual recordScreenshot optionFull-page image
Feed an LLMMarkdown outputClean Markdown text

Two practical notes. First, render_js and stealth_proxy are the two options that most change both success rate and credit cost, so decide them deliberately. Second, extraction rules are only as good as the selectors — a rule that matches nothing returns nothing, which is different from a blocked request.

Estimating credit cost before you run a batch

Credit consumption is driven by the options on each request, not by the target site. The captured per-request rates are:

  • Base request: starts at 1 credit.
  • JavaScript rendering enabled: 5 credits per successful request.
  • Premium proxy without JS rendering: 10 credits.
  • Premium proxy with JS rendering: 25 credits.
  • stealth_proxy: 75 credits.

So a 1,000-page price sweep with JS rendering enabled works out to roughly 5,000 credits, while the same sweep on stealth_proxy works out to roughly 75,000. That gap is the single biggest planning decision on this page. Run a small pilot — 20 to 50 URLs — with the cheapest option that succeeds, and only escalate to premium or stealth proxies for the subset that fails.

The captured plan terms also state that credits are valid for one month and do not roll over, so size your monthly batch to the plan rather than stockpiling. Treat both the rates and the validity rule as terms to confirm with the account owner before you commit budget.

Blocked page vs. empty extraction

Two failure modes look similar in a log and need different fixes.

  • Blocked request. The response is a challenge or block page rather than book content. Fix: enable render_js, then stealth_proxy if the block persists. This is a delivery problem.
  • Empty extraction. The page rendered fine but your extract_rules returned nothing. Fix: re-check the selector against the current page markup, or switch to ai_extract_rules and describe the field in plain language. This is a targeting problem.

A quick triage: if the response contains book text at all, you are in the second case. If it contains a challenge, you are in the first. Logging the raw response for the first few failures of any new job saves hours later.

From signup to first request

The path is short: create an account to receive an API key, then send a request with the target Rakuten Books URL to the endpoint and authentication header your account supplies. The service handles rendering, proxy rotation and bot bypass on its side.

SDKs are offered for Python, Node.js, Go, PHP, Ruby and Java, and plain cURL works too, so you can stay in whatever stack you already run — confirm the current package names and distribution channels with the owner before wiring them into a build. A dashboard request builder lets you test a URL without writing code first, which is useful for confirming a page renders before you build the loop around it.

The captured signup offer is 1,000 free credits with no card required; confirm that allowance is still current before you plan a pilot around it.

A sensible first run: one book page, default options, inspect the JSON, then add extract_rules for the fields you actually need.

Captured plan reference (unverified, pending owner confirmation)
PlanPriceAPI creditsConcurrent requestsPriority supportAccount managerTeam management
Hobby$19 /mo75,00025Not includedNot includedNot included
Freelance$49 /mo250,00050Not includedNot includedNot included
Startup (Recommended)$99 /mo1,000,000100Not includedNot includedNot included
Business$249 /mo3,000,000200IncludedIncludedIncluded
Business +$599 /mo8,000,000400IncludedIncludedIncluded
Enterprise 14$999 /mo14,000,000500IncludedIncludedIncluded
Enterprise 24$1,599 /mo24,000,000600IncludedIncludedIncluded
Enterprise 41 (Recommended)$2,399 /mo41,000,000700IncludedIncludedIncluded
Enterprise 69$3,599 /mo69,000,000800IncludedIncludedIncluded
Enterprise 120$5,799 /mo120,000,000900IncludedIncludedIncluded

Prices are exclusive of VAT. All plans include JavaScript rendering, rotating and premium proxies, geotargeting, and screenshots and extraction rules. These figures are a dated, unverified capture from the publisher's plan page — not current owner terms. Confirm pricing, credit allowances and support commitments with the account owner before purchase.

Frequently asked questions

Do I need a Rakuten account to scrape Rakuten Books?

No. You only need an API key from the scraping service. The captured signup offer includes 1,000 free credits with no card required — confirm that allowance is still current before you rely on it. Send the public Rakuten Books URL and the service handles the rest.

Is scraping Rakuten Books legal?

Public-facing pages can usually be scraped, but review the target site's terms of service before deploying and avoid post-login content. Treat this as a compliance check you perform, not a blanket permission.

What data can I extract from Rakuten Books?

Anything that renders on the public page. Catalogue fields include title, author, publisher, price, ISBN, publication date, page count and customer ratings. For anything beyond that, use extract_rules with CSS selectors or ai_extract_rules for AI-driven extraction to get structured JSON back.

How do I start scraping Rakuten Books?

Sign up, take your API key, and send a request with the target URL to the endpoint and authentication header your account supplies. The service renders the page, rotates proxies and returns the data. The captured offer includes 1,000 free credits to test; confirm it is still current.

Which programming languages can I use?

Any. SDKs are offered for Python, Node.js, Go, PHP, Ruby and Java, and plain cURL works too. Pick whatever your stack already uses, and confirm the current package names and distribution channels with the owner before adding them to a build.

How much does it cost to scrape Rakuten Books?

The captured offer is 1,000 free credits on signup with no card required, and paid plans start at $19/month for higher volume and concurrency — confirm both with the owner. Per-request credit cost depends on options: 5 credits for JS rendering, 25 for a premium proxy with JS, and 75 for stealth_proxy.

Why did my extraction return empty JSON?

An empty result usually means the selector did not match the current page markup, not that the request was blocked. Check the selector against the live page, or switch to ai_extract_rules and describe the field in plain language. If the response is a challenge page instead of book content, enable render_js and then stealth_proxy.