Skip to content

eBook Listings and Metadata, Scraping Ready

Public eBook catalog pages often load their content with JavaScript and sit behind bot detection.

OUTPUT FORMATSHTMLJSONMarkdown

This API takes a catalog URL, runs the page in a real browser, rotates the IP, and returns the rendered response or parsed fields so your client can stay a thin HTTP call.

What you can collect from public eBook pages

A public catalog page can expose several useful datasets. The most common are title and publication metadata, reader ratings, and author information. The API is built to return those fields where the page exposes them, not to invent values that are absent.

Typical fields include title, author, ISBN, publication date, publisher, rating, review count, and download count. Category and download count are also listed among the parseable fields on catalog pages. Treat any field that is missing from a particular page as unavailable for that page rather than as an error in the request.

Use the field list as a checklist when you design your output schema. If a field matters to your analysis, confirm that the target page actually renders it before you build a pipeline around it.

Three datasets worth extracting

Metadata. Titles, authors, publication dates, ISBNs, ratings, and download counts support publishing analysis and content discovery. A catalog page is usually the best place to start because it groups those attributes in one record.

Ratings. Reader ratings and review counts help you compare titles and spot preference trends. Use them as one input to competitive analysis, not as a standalone measure of quality.

Author information. Author pages and author fields reveal relationships between writers and their works. That supports targeted research and business strategy work.

Each dataset can be collected separately or combined into a single record per title. Combining them is usually more useful because it lets you join ratings to authors and metadata without a second pass.

How the request flow works

  1. Create an account to get an API key and the free starting credits.
  2. Install a client for your stack, or send a plain HTTP request. Python, Node.js, Go, PHP, Ruby, and Java clients are published, and cURL works too.
  3. Send the eBook URL with your API key. The renderer executes the page in a real browser, rotates the IP, and returns a response your scraper can act on.
  4. Add advanced parameters only when the page needs them: render_js for JavaScript, stealth_proxy for CAPTCHA-heavy pages, country_code for geo-targeting, and ai_extract_rules for natural-language extraction.

The first request is best made in the dashboard request builder. Once the response looks right, copy the generated snippet into your codebase.

Field and control map

Use this map to decide which request option affects which part of the result.

  • Page rendering: render_js makes the browser execute JavaScript before the response is captured. Use it when the catalog content is not present in the raw HTML.
  • Bot and CAPTCHA handling: stealth_proxy routes the request through a stealth proxy. Use it when the target blocks ordinary requests.
  • Geo variation: country_code routes through a residential IP in the chosen country. Use it when prices, availability, or catalog content vary by region.
  • Structured output: extract_rules maps CSS selectors to field names. ai_extract_rules accepts a natural-language specification instead. Either way, the response comes back as parsed JSON.
  • Screenshots and extraction: the plan comparison includes screenshots and extraction rules as a combined capability.

Concurrency is a per-plan limit on simultaneous requests. It is not a per-target rate limit. If a target throttles aggressive patterns, space out requests or use multiple sessions.

Worked example: one catalog page, one record

Suppose a public catalog page lists a single title with an author, an ISBN, a publication date, a publisher, a rating, a review count, and a download count. A minimal request sends that URL with your API key. If the page renders its content with JavaScript, add render_js. If the page blocks ordinary requests, add stealth_proxy.

To receive named fields rather than raw HTML, supply extract_rules with CSS selectors mapped to field names, or supply ai_extract_rules with a natural-language description of the fields you want. The response is parsed JSON. A record from this page would carry the title, author, ISBN, date, publisher, rating, review count, and download count that the page exposes.

If a field is absent from the response, check two things in order: first, whether the page actually renders that field in a browser; second, whether your selector or natural-language rule names it precisely. A missing field is usually an extraction-rule problem, not a rendering problem, once the page has rendered successfully.

Rendering failure vs. extraction failure

These two failure modes look similar in a log but need different fixes.

Rendering failure. The page content never arrives. Symptoms include an empty body, a challenge page, or a response that lacks the catalog record entirely. Fixes: enable render_js, add stealth_proxy, or change country_code if the content is geo-restricted.

Extraction failure. The page content arrives, but the JSON is missing fields or contains the wrong values. Fixes: correct the CSS selectors in extract_rules, tighten the natural-language specification in ai_extract_rules, or confirm that the field is actually present on the page.

A quick diagnostic: fetch the page with rendering enabled and inspect the raw response. If the target text is present, the problem is in the extraction rules. If it is absent, the problem is in rendering or access.

Plans and credit costs

The plan comparison table below lists the standard and enterprise tiers with their monthly credit allowances and concurrency limits. Prices are shown exclusive of VAT. Credits are valid for one month and do not roll over. Requests start at one credit each, and options add cost: JavaScript rendering costs 5 credits per successful request. Premium proxies cost 10 credits when JavaScript rendering is disabled and 25 credits when it is enabled; the 25-credit figure is the premium_proxy-with-JS rate. stealth_proxy costs 75 credits.

A free starting allowance is available without a card. Paid plans begin at the entry tier shown in the table. Use the table to compare credit volume and concurrency rather than to assume a fixed cost per page, because the per-request cost depends on the options you enable.

Compliance and scale notes

The service is described as GDPR and CCPA compliant and states that it does not collect or store personal data from scraped sites unless the user explicitly requests it. Proxy rotation and headless browser rendering are used to reduce IP-based blocking and to mimic ordinary browsing behavior.

The platform is built to scale across many headless browsers and rotating proxies. Reported response times are in the range of one to five seconds across most sites, including JavaScript-heavy ones. Treat those figures as published performance claims and validate them against your own targets before committing to a volume plan.

Plan comparison
PlanPriceAPI creditsConcurrent requestsJavaScript renderingRotating & premium proxiesGeotargetingScreenshots & extraction rulesPriority email supportDedicated account managerTeam management
Hobby$19 /mo75,00025IncludedIncludedIncludedIncludedNot includedNot includedNot included
Freelance$49 /mo250,00050IncludedIncludedIncludedIncludedNot includedNot includedNot included
Startup (Recommended)$99 /mo1,000,000100IncludedIncludedIncludedIncludedNot includedNot includedNot included
Business$249 /mo3,000,000200IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Business +$599 /mo8,000,000400IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Enterprise 14$999 /mo14,000,000500IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Enterprise 24$1,599 /mo24,000,000600IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Enterprise 41 (Recommended)$2,399 /mo41,000,000700IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Enterprise 69$3,599 /mo69,000,000800IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Enterprise 120$5,799 /mo120,000,000900IncludedIncludedIncludedIncludedIncludedIncludedIncluded

All prices are exclusive of VAT. Credits are valid for one month and do not roll over. Requests start at one credit each; JavaScript rendering costs 5 credits, premium proxies cost 10 credits without JavaScript rendering and 25 credits with it, and stealth_proxy costs 75 credits. Plan prices and allowances are captured reference figures and should be checked against current pricing before purchase.

Frequently asked questions

Do I need an account to scrape eBook data?

You need an API key, which you get by signing up. The free starting allowance does not require a card. Once you have the key, send the URL and the service handles rendering and proxy rotation.

Can I scrape eBook data from a specific country?

Yes. Pass country_code on the request to route through a residential IP in that country. This is useful when catalog content, pricing, or availability varies by geography.

What's the rate limit for scraping eBook data?

Limits are on concurrency per plan, not on requests per target. If a target throttles aggressive patterns, space out requests or use multiple sessions. The plan table lists the concurrency figure for each tier.

How do I get structured JSON from eBook data?

Pass extract_rules with CSS selectors mapped to field names, or use ai_extract_rules with a natural-language specification. The response is parsed JSON.

Which programming languages can I use to scrape eBook data?

Any language that can send an HTTP request. Published clients cover Python, Node.js, Go, PHP, Ruby, and Java, and plain cURL works too.

How much does it cost to scrape eBook data?

A free starting allowance is available without a card. Paid plans begin at the entry tier in the plan table. Per-request cost depends on options: JavaScript rendering costs 5 credits. Premium proxies cost 10 credits without JavaScript rendering and 25 credits with it (the premium_proxy-with-JS rate). stealth_proxy costs 75 credits.