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

Audiomack Scraper

Extract trending tracks, artist pages, playlist data, and streaming stats from Audiomack music platform. Built on spider-browser .

Get started Docs
target
audiomack.com
success rate
99.9%
latency
~4ms
POST /fetch/audiomack.com/
return_format
curl -X POST https://api.spider.cloud/fetch/audiomack.com/ \
  -H "Authorization: Bearer $SPIDER_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"return_format": "json"}'
200 OK · cache hit · response shape
{
  "url": "https://audiomack.com/",
  "status": 200,
  "data": {
    "track_title": "string",
    "artist": "string",
    "plays": "string",
    "favorites": "string",
    "genre": "string",
    "duration": "string",
    "album": "string",
    "upload_date": "string"
  }
}
Quick start

Extract data in minutes.

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

audiomack-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://audiomack.com/trending-now");
await page.content();

const data = await page.extractFields({
  title: ".song-title a",
  artist: ".song-artist a",
  plays: ".song-plays",
  image: { selector: ".song-artwork img", attribute: "src" },
});

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

Fields you can pull.

Track titleArtistPlaysFavoritesGenreDurationAlbumUpload date
Metadata

Track & album data

Extract track info, artist data, and play counts from audiomack.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 audiomack.com.

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