Skip to main content
AI Studio  add-on for Spider.
Music & Podcasts
pocketcasts.com Verified

Pocket Casts Scraper

Extract podcast discover pages, trending shows, episode data, and curator picks from Pocket Casts directory. Built on spider-browser .

Get started Docs
target
pocketcasts.com
success rate
99.9%
latency
~4ms
POST /fetch/pocketcasts.com/
return_format
curl -X POST https://api.spider.cloud/fetch/pocketcasts.com/ \
  -H "Authorization: Bearer $SPIDER_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"return_format": "json"}'
200 OK · cache hit · response shape
{
  "url": "https://pocketcasts.com/",
  "status": 200,
  "data": {
    "show_title": "string",
    "author": "string",
    "category": "string",
    "episode_count": "string",
    "description": "string",
    "rating": "string"
  }
}
Quick start

Extract data in minutes.

Structured JSON from pocketcasts.com with a single POST. AI-resolved selectors, cached on the first call.

pocket-casts-scraper.ts
import { SpiderBrowser } from "spider-browser";

const spider = new SpiderBrowser({
  apiKey: process.env.SPIDER_API_KEY!,
});

await spider.connect();
const page = spider.page!;
await page.goto("https://www.pocketcasts.com/discover/");
await page.content();

const data = await page.extractFields({
  title: ".podcast-card__title",
  author: ".podcast-card__author",
  category: ".podcast-card__category",
  image: { selector: ".podcast-card__artwork img", attribute: "src" },
});

console.log(data);
await spider.close();
ready to run · spider-browser · TypeScript
Extraction

Fields you can pull.

Show titleAuthorCategoryEpisode countDescriptionRating
Metadata

Track & album data

Extract track info, artist data, and play counts from pocketcasts.com.

Rendering

Player handling

Handle embedded players, dynamic playlists, and streaming interfaces.

Scale

Catalog coverage

Process entire artist catalogs and podcast libraries at scale.

Related

More Music & Podcasts scrapers.

Start

Start scraping pocketcasts.com.

Grab an API key and call the endpoint above. The first request resolves the config; every request after hits cache.