Audible Audiobook Search Scraper

What does Audible Audiobook Search Scraper do?

Audible Audiobook Search Scraper collects structured, publicly visible audiobook records from Audible search pages. It is a lightweight Audible API alternative for keyword research, catalog monitoring, and repeatable dataset collection. It uses the public search surface at https://www.audible.com and does not sign in, solve CAPTCHAs, bypass paywalls, or access private information.

Why use Audible Audiobook Search Scraper?

Use the Actor when you need a bounded list of audiobooks without manually copying search results. Each result can include the title, ASIN, product URL, authors, narrators, series, duration, release date, language, rating, rating count, price, cover image, publisher, and public merchandising labels.

The Actor supports Audible country domains, result limits from 1 to 100, and the existing sort options in the input schema. Results are deduplicated across pages. Pagination is generated deterministically and bounded to at most six public pages. Apify scheduling, API access, webhooks, monitoring, and optional proxy configuration can be used around the Actor according to your account and the target site's terms. Proxy use is disabled by default. The Actor uses HTTP and Cheerio rather than launching a browser.

What data can it extract?

Field	Type	Description
recordType	string	Always audiobook in the dataset
asin	string	Public Audible product identifier
title	string	Audiobook title
productUrl	string	Public product URL
authors	array	Public author names
narrators	array	Public narrator names
series	string	Series label when shown
rating, ratingsCount	number	Public average rating and count
price, currency	number, string	Price shown on the result card
length, releaseDate, language	string	Public catalog labels
summary, coverImageUrl, publisher	string	Public descriptive fields
searchQuery, country, scrapedAt	string	Run context and timestamp

When Audible returns a site-error shell, CAPTCHA, login, paywall, rate-limit, device-verification, access-control, or country-redirect page, the Actor stops without bypassing it. Failure evidence is bounded in OUTPUT; the dataset contains audiobook rows only. A run with neither verified rows nor an explicit empty-result page fails closed with an empty dataset.

How to scrape Audible audiobook search results

1. Open the Input tab and enter a public Audible search query.
2. Choose maxItems, country, sortBy, and proxyConfiguration if needed.
3. Click Start. The Actor follows public search-result pages until the limit or the end of pagination is reached.
4. Open the Dataset tab to inspect records, or use the API tab to download them.

You can download the dataset in formats such as JSON, HTML, CSV, or Excel.

Example input

{
  "query": "example audiobook",
  "maxItems": 20,
  "country": "us",
  "sortBy": "relevance",
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}

How much will it cost?

Cost depends on the number of result pages, HTTP runtime, and any proxy configuration used by your run. Start with a small maxItems value while checking coverage, then schedule larger runs only when the public search page is available and your usage complies with Audible's terms.

Tips and advanced options

• Keep maxItems reasonable for a single run and use scheduling for recurring monitoring.
• Use the country that matches the public Audible domain you intend to query.
• A residential proxy may help with ordinary network availability, but it is not used to bypass access controls.
• Read OUTPUT for run status, page counts, valid-empty state, and bounded failures.

Example output

{
  "recordType": "audiobook",
  "position": 1,
  "asin": "B000000000",
  "title": "Example Audiobook Title",
  "authors": ["Example Author"],
  "narrators": ["Example Narrator"],
  "rating": 4.5,
  "price": 24.99,
  "currency": "$",
  "searchQuery": "example query",
  "scrapedAt": "2026-08-18T12:00:00.000Z"
}

Key-value store

After processing, the Actor writes a strict JSON run summary under the OUTPUT key. It contains product and unique counts, page/request counts, query/storefront/sort context, proxy use, valid-empty state, bounded failures, and elapsed time.

FAQ, disclaimers, and support

Does the Actor require an Audible account?

No. It uses publicly visible search pages only. If a page requires sign-in, payment, verification, or another access step, the Actor stops and reports a diagnostic instead of attempting to continue.

Can it scrape private user data?

No. Our Actors are ethical and do not extract private user data, such as email addresses, gender, or location. They only extract what the user has chosen to share publicly. Results could still contain personal data. Personal data is protected by the GDPR in the European Union and by other regulations around the world. Do not scrape personal data unless you have a legitimate reason to do so. If you are unsure whether your reason is legitimate, consult your lawyers.

For troubleshooting, review the run log and OUTPUT. Use the Issues tab for feedback and the API tab for programmatic access.