Audiobook Metadata in Clean, Structured JSON
Audiobook catalog pages hold the fields a recommendation engine, comparison tool, or taxonomy needs: title, narrator, runtime, publisher, series, release date, rating, review count, and price.
This API takes a catalog URL and returns that data as parsed JSON or as rendered HTML, so the pipeline does not need its own headless browser fleet or proxy pool. The sections below explain which request controls change the output, which change the cost, and how to tell a block apart from a throttle.
What a catalog page returns
The field set is fixed even though the values are not. Every audiobook catalog page carries title, narrator, runtime, publisher, series, release date, rating, review count, and price; ratings and prices drift, so treat each pull as a timestamped snapshot and re-fetch before you act on it.
Which workflow to run first depends on what you already have. If you are starting from nothing, a catalog sweep by genre gives you titles and narrators to seed a recommendation engine or a competitor comparison. If you already have titles and need positioning context, an author-details pull is the narrower job. If the goal is discovery rather than inventory, a genre-tag pull is the one that pays off, because it turns a flat list of titles into a browsable taxonomy. Running all three at once usually means paying for fields you will not use yet; pick the one your product needs next.
Request controls and what each one changes
Four parameters do most of the work on audiobook pages. render_js=true runs the page in a real headless browser and returns post-render HTML, which matters when narrator or price data is injected by client-side script. stealth_proxy adds a stronger proxy path when a target responds aggressively to ordinary traffic. country_code routes the request through a residential IP in the chosen country, useful when catalog content or pricing varies by region. extract_rules maps CSS selectors to field names for parsed JSON, and ai_extract_rules accepts a natural-language spec instead of selectors. The first two change cost as well as behavior; the last two change output shape.
How credits map to requests
Plans are sized in API credits and concurrent requests. Credits are valid for one month and do not roll over, and requests start at one credit each. Turning on JS rendering raises a successful request to five credits. Premium proxies cost ten credits with rendering off and twenty-five with rendering on. That means a rendered, premium-proxied audiobook pull consumes twenty-five credits, so a 75,000-credit plan covers roughly 3,000 such requests rather than 75,000. Estimate the mix of plain, rendered, and premium-proxied calls before picking a tier; the concurrency figure caps simultaneous requests, not monthly volume.
Worked example: a genre sweep without over-rendering
Say you want every title in one genre and expect a few hundred pages. Start with plain requests at one credit each and map the nine fields with extract_rules. Inspect the results: if title, narrator, and publisher come back populated but runtime and price are empty, those two fields are almost certainly rendered client-side. Re-run only the affected pages with render_js=true at five credits each instead of re-pulling the whole batch. If a subset of pages returns challenge interstitials rather than data, add stealth_proxy to just those. The saving is straightforward: a 300-page sweep where 60 pages need rendering costs 240 plain credits plus 300 rendered credits, not 1,500 credits for rendering everything.
Telling a block apart from a throttle
Three failure shapes look similar and need different fixes. A block usually shows as a CAPTCHA or an interstitial before the catalog content loads; the response is a challenge page rather than the expected fields. A throttle shows as repeated refusals or timeouts from the same target while other targets still respond; the API applies concurrency limits per plan rather than per-target rate limits, so spacing requests out or splitting them across sessions is the lever. A missing-data result is different again: the request succeeds and returns HTML, but the fields are absent because the page renders them client-side; render_js=true is the fix there. Check which of the three you are seeing before changing plans or adding proxies.
Field map: selectors versus natural-language extraction
Use extract_rules when the target page structure is stable and you can name the CSS selectors for each field. Use ai_extract_rules when the page markup shifts between releases or when the field set is described more easily in words than in selectors. Either path returns parsed JSON. The fields worth mapping explicitly are title, narrator, runtime, publisher, series, release date, rating, review count, and price. If a field is missing from the response, confirm first whether the page actually contains it after rendering; a selector that points at a lazy-loaded element will return empty even when the value is visible in a browser.
From URL to parsed data
The workflow is short. Create an account to get an API key and starting credits. Install the SDK for your stack, or call the endpoint directly with the key and the audiobook URL. The service rotates proxies, spoofs fingerprints, and renders JavaScript behind the scenes, then returns a response ready to parse. For teams that prefer to configure visually, the dashboard request builder accepts a URL and parameters and generates a snippet in Python, Node, Go, PHP, Ruby, or cURL. Test in the builder first, then move the generated snippet into the codebase.
| Plan | Price | API credits | Concurrent requests | JS rendering | Rotating & premium proxies | Geotargeting | Screenshots & extraction rules | Priority email support | Dedicated account manager | Team management |
|---|---|---|---|---|---|---|---|---|---|---|
| Hobby | $19 /mo | 75,000 | 25 | Included | Included | Included | Included | Not included | Not included | Not included |
| Freelance | $49 /mo | 250,000 | 50 | Included | Included | Included | Included | Not included | Not included | Not included |
| Startup (Recommended) | $99 /mo | 1,000,000 | 100 | Included | Included | Included | Included | Not included | Not included | Not included |
| Business | $249 /mo | 3,000,000 | 200 | Included | Included | Included | Included | Included | Included | Included |
| Business + | $599 /mo | 8,000,000 | 400 | Included | Included | Included | Included | Included | Included | Included |
| Enterprise 14 | $999 /mo | 14,000,000 | 500 | Included | Included | Included | Included | Included | Included | Included |
| Enterprise 24 | $1,599 /mo | 24,000,000 | 600 | Included | Included | Included | Included | Included | Included | Included |
| Enterprise 41 (Recommended) | $2,399 /mo | 41,000,000 | 700 | Included | Included | Included | Included | Included | Included | Included |
| Enterprise 69 | $3,599 /mo | 69,000,000 | 800 | Included | Included | Included | Included | Included | Included | Included |
| Enterprise 120 | $5,799 /mo | 120,000,000 | 900 | Included | Included | Included | Included | Included | Included | Included |
Prices are exclusive of VAT. Credits are valid for one month and do not roll over; requests start at one credit each. JS rendering costs 5 credits per successful request; premium proxies cost 10 credits without rendering and 25 with rendering. Geotargeting covers 200+ countries and territories (40+ on classic proxies). Plan prices and inclusions are a dated reference and should be checked against current pricing before purchase.
Frequently asked questions
Will I get blocked when scraping audiobook metadata?
Requests are routed through rotating residential proxies and a real headless browser, so they resemble ordinary traffic. If a particular target becomes aggressive, add stealth_proxy to the request for a stronger proxy path.
Can I scrape audiobook metadata without writing code?
Yes. The dashboard request builder accepts a URL and parameters and produces a ready-to-copy snippet in Python, Node, Go, PHP, Ruby, or cURL. You can test the request there before moving the snippet into a codebase.
How do I handle JavaScript when scraping audiobook metadata?
Set render_js=true. The page runs in a real headless browser, the JavaScript executes server-side, and the response contains the post-render HTML, which is what you need when narrator, price, or rating values are injected client-side.
Can I scrape audiobook metadata from a specific country?
Yes. Pass country_code on the request to route through a residential IP in that country. This matters when catalog availability, pricing, or regional editions differ by geography.
What's the rate limit for scraping audiobook metadata?
The API applies concurrency limits per plan rather than per-target rate limits. If a target throttles aggressive patterns, space requests out or split them across multiple sessions.
How do I get structured JSON from audiobook metadata?
Pass extract_rules with CSS selectors mapped to field names, or use ai_extract_rules with a natural-language description of the fields. Either way the response comes back as parsed JSON.
How many audiobook pages can a plan cover?
Divide the plan's credit allowance by the per-request cost. A plain request costs one credit, a rendered request five, a premium-proxied request ten, and a rendered premium-proxied request twenty-five. A 75,000-credit plan therefore covers about 3,000 rendered premium-proxied pulls, or far more plain ones. Credits expire monthly and do not roll over.
Which fields should I map first?
Start with title, narrator, runtime, publisher, series, release date, rating, review count, and price, since those are the fields a catalog page returns. Map them with extract_rules if the markup is stable, or describe them with ai_extract_rules if the layout changes between releases.