# Bandcamp Music Scraper (`solidcode/bandcamp-music-scraper`) Actor

\[💰 from $2 / 1K] Extract Bandcamp artists, labels, albums, tracks, and fans. Scrape full discographies, track listings with audio previews, prices, tags, and supporter lists from URLs, keyword search, or genre and location discovery.

- **URL**: https://apify.com/solidcode/bandcamp-music-scraper.md
- **Developed by:** [SolidCode](https://apify.com/solidcode) (community)
- **Categories:** Developer tools, E-commerce, Other
- **Stats:** 6 total users, 0 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $12.00 / 1,000 albums

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Bandcamp Music Scraper

Pull artists, labels, albums, tracks, and fans from Bandcamp at scale — full discographies, normalized prices, release dates, genre tags, cover art, 30-second preview MP3 links for every streamable track, and supporter lists for every release. Paste a single artist URL and collect their entire catalog, search by keyword across four result kinds, or browse 27 Discover genres by location. Built for music marketers, A\&R scouts, playlist curators, and music-data teams who need structured Bandcamp catalog data without clicking through hundreds of release pages by hand.

### Why This Scraper?

- **Full discography from one URL** — paste a single artist or label page and collect every release in their catalog, even hundreds or thousands of titles, with no per-album links to assemble.
- **30-second preview MP3 URLs for every streamable track** — each track row carries duration, track number, and a direct audio preview link wherever Bandcamp streams that track (artists set this per track, so a label sampler may stream only one), ready to feed audio-analysis, fingerprinting, or playlist tools.
- **27 Discover genres with location targeting** — browse trending releases from Electronic to Jazz to Ambient, narrowed to a place like Berlin, Tokyo, or Los Angeles, sorted by Best Selling, Newest Arrivals, or Surprise Me.
- **Four keyword search modes** — one keyword returns matching artists & labels, albums, tracks, or fans — or all kinds at once — so you find catalog data without knowing the URL first.
- **Supporter/fan lists most scrapers skip** — pull the fans who bought or wishlisted a release (username and profile link), up to 500 per release, a whole Bandcamp entity competitors omit.
- **Normalized prices and currencies** — fixed-price releases report a clean major-unit price with a 3-letter ISO currency, while the name-your-price and free-download releases Bandcamp sells with no set price come back with an empty price instead of an invented one, roughly one album in seven and up to a third on some genre searches; every album, single, and track row carries the currency.
- **Four record types, each on its own clean tab** — artist/label, album, track, and fan rows all carry one `recordType` field, and every run splits them into separate Albums & Tracks, Artists & Labels, and Fans tabs (plus an Overview with everything), so each entity is ready to route downstream without untangling.
- **Artist & label profiles in full** — name, bio, self-reported location, genre tags, header image, social links, and release count, with a label flag to separate imprints from solo artists.
- \**Custom domains and *.bandcamp.com alike** — point it at a band's own domain or a Bandcamp subdomain and get the same structured catalog either way.

### Use Cases

**Music Market Research**

- Track which releases are best-selling in a genre week over week
- Map a label's full catalog, release cadence, and pricing strategy
- Compare genre trends across cities using location-targeted discovery
- Benchmark independent pricing across albums, tracks, and name-your-price releases

**A\&R & Talent Scouting**

- Surface newest arrivals in a genre to spot rising independent artists early
- Pull an artist's complete discography to assess output and consistency
- Find artists by location to scout regional scenes (e.g. Berlin techno, Tokyo city pop)
- Build watchlists of artists from Artist Recommended Discover picks

**Playlist & Catalog Building**

- Collect 30-second preview URLs for streamable tracks to audition them programmatically
- Assemble themed catalogs by genre, location, or keyword search
- Enrich a music database with cover art, release dates, and genre tags
- Source independent tracks for licensing and sync libraries

**Fan & Audience Analysis**

- Pull supporter lists to understand who backs a release
- Identify superfans who appear across an artist's multiple releases
- Map an artist's audience overlap with peers in the same genre
- Build outreach lists from fan profiles for community-building campaigns

### Getting Started

#### Scrape One Album

The simplest run — paste an album URL and get the release plus its full tracklist:

```json
{
    "startUrls": ["https://machinegirl.bandcamp.com/album/wlfgrl"],
    "maxResults": 50
}
```

#### Crawl a Full Discography

Point at an artist or label page to collect every release they have:

```json
{
    "startUrls": ["https://machinegirl.bandcamp.com/"],
    "includeTracks": true,
    "maxResults": 500
}
```

#### Search by Keyword

Find albums matching a keyword without knowing any URLs:

```json
{
    "searchTerms": ["lo-fi hip hop", "Aphex Twin"],
    "searchType": "albums",
    "maxResults": 100
}
```

#### Discover by Genre and Location

Browse the best-selling ambient releases out of Berlin:

```json
{
    "discoverGenre": "ambient",
    "discoverLocation": "berlin",
    "sortBy": "top",
    "maxResults": 200
}
```

#### Album with Supporters

Pull one release and the fans who backed it:

```json
{
    "startUrls": ["https://machinegirl.bandcamp.com/album/wlfgrl"],
    "includeFans": true,
    "maxResults": 600
}
```

### Input Reference

#### What to Scrape

| Parameter | Type | Default | Description |
|-----------|------|---------|-------------|
| `startUrls` | string\[] | `["https://machinegirl.bandcamp.com/"]` | Bandcamp links — the type is auto-detected. An artist or label page collects every release in their discography; an album or track page returns that release. Works for `*.bandcamp.com` and custom domains. |
| `searchTerms` | string\[] | `[]` | Keywords to look up on Bandcamp — an artist name, album title, or genre. Each keyword returns up to 50 matching results, so add several related keywords for a wider sweep. |

#### Search Filters

| Parameter | Type | Default | Description |
|-----------|------|---------|-------------|
| `searchType` | select | `All Types` | Which kind of result your keywords return: All Types, Artists & Labels, Albums, Tracks, or Fans. Applies only to Search Keywords. |

#### Discovery Filters

| Parameter | Type | Default | Description |
|-----------|------|---------|-------------|
| `discoverGenre` | select | `None` | Browse trending releases in one of 27 genres (Electronic, Rock, Metal, Hip-Hop / Rap, Experimental, Ambient, Jazz, and more). Leave as None to skip genre discovery. |
| `discoverLocation` | string | `""` | Narrow genre discovery to a place such as `berlin`, `tokyo`, or `los angeles`. Leave empty for worldwide results. Applies only when a genre is selected. |
| `sortBy` | select | `Best Selling` | Order for genre discovery: Best Selling, Newest Arrivals, or Surprise Me. |

#### Options

| Parameter | Type | Default | Description |
|-----------|------|---------|-------------|
| `maxResults` | integer | `100` | Maximum results across all URLs, searches, and discovery. Set to `0` for unlimited. Each keyword contributes at most 50 matches, so a high number needs artist URLs, more keywords, or genre discovery to fill it. Start with 10–50 to test, then increase. |
| `includeTracks` | boolean | `true` | For each release, also return its full tracklist with titles, durations, and track numbers, plus a 30-second preview link for every track Bandcamp streams. Turn off for a lighter, release-only dataset. |
| `includeFans` | boolean | `false` | For each album, also return the fans who bought or wishlisted it. Capped at 500 supporters per release to keep runs predictable. Leave off unless you need supporter data. |

### Output

Every row carries a `recordType` field — `artist`, `album`, `track`, or `fan` — so you can filter each entity cleanly downstream. The Overview tab holds every record from the run, while the Albums & Tracks, Artists & Labels, and Fans tabs each show only their own record type (the Fans tab is present only when Include Supporters is enabled).

#### Artist / Label (`recordType: "artist"`)

```json
{
    "recordType": "artist",
    "name": "Machine Girl",
    "isLabel": false,
    "bio": "Machine Girl is an American electronic music duo from Long Island, New York.",
    "location": "Long Island, NY",
    "imageUrl": "https://f4.bcbits.com/img/0012345678_10.jpg",
    "tags": ["breakcore", "electronic", "hardcore", "New York"],
    "socialLinks": {
        "instagram": "https://instagram.com/machinegirlmusic",
        "twitter": "https://twitter.com/machinegirlz"
    },
    "numAlbums": 14,
    "url": "https://machinegirl.bandcamp.com/"
}
```

| Field | Type | Description |
|-------|------|-------------|
| `recordType` | string | Always `"artist"` |
| `name` | string | Artist or label name |
| `isLabel` | boolean | `true` when the page is a label/imprint |
| `bio` | string | Profile bio / about text |
| `location` | string | Self-reported location; `null` when the profile leaves it blank |
| `imageUrl` | string | Header / avatar image URL |
| `tags` | string\[] | Genre tags, drawn from the artist's own releases |
| `socialLinks` | object | External links keyed by site (website, instagram, twitter, youtube, etc.) |
| `numAlbums` | number | Number of releases in the discography |
| `url` | string | Profile URL |

#### Album (`recordType: "album"`)

```json
{
    "recordType": "album",
    "title": "WLFGRL",
    "artist": "Machine Girl",
    "type": "album",
    "url": "https://machinegirl.bandcamp.com/album/wlfgrl",
    "imageUrl": "https://f4.bcbits.com/img/a0012345678_10.jpg",
    "releaseDate": "2014-04-21T00:00:00Z",
    "priceAmount": 7.0,
    "currency": "USD",
    "downloadAvailable": true,
    "tags": ["breakcore", "electronic", "hardcore"],
    "numTracks": 11,
    "artistLocation": "Long Island, New York"
}
```

| Field | Type | Description |
|-------|------|-------------|
| `recordType` | string | `"album"` |
| `title` | string | Album title |
| `artist` | string | Artist or label name |
| `type` | string | Release type label from Bandcamp |
| `url` | string | Release URL |
| `imageUrl` | string | Cover art URL |
| `releaseDate` | string | Release date in ISO 8601 UTC (`YYYY-MM-DDTHH:MM:SSZ`), so it sorts and filters correctly in any tool; `null` when Bandcamp lists no date |
| `priceAmount` | number | Price as a major-unit float; `null` for name-your-price or free |
| `currency` | string | 3-letter ISO currency code |
| `downloadAvailable` | boolean | Whether a digital download is offered |
| `tags` | string\[] | Genre tags |
| `numTracks` | number | Number of tracks on the release |
| `artistLocation` | string | Artist or label's self-reported location; `null` when they left it blank |

#### Track (`recordType: "track"`)

Emitted for every standalone single in an artist's or label's discography, for any track URL or track search hit, and for each track on an album when `includeTracks` is on. Those three routes fill the date and price differently, and the difference is worth knowing before you pick a mode:

| How the track row appears | `releaseDate` | `priceAmount` |
|---------------------------|---------------|---------------|
| A track inside an album, returned by **Include Track Listings** | empty | empty |
| An album track you asked for by its own track URL, or that came back from a track search | empty | filled |
| A standalone single, sold as a release in its own right | filled | filled |

Empty means Bandcamp genuinely publishes no such value for that shape: a tracklist entry has neither a date nor a price of its own, and an album track has no release date apart from the album's. A price is also empty on a name-your-price or free track, exactly as on albums.

A track from an album's tracklist, the shape **Include Track Listings** returns. The preview link, duration and position are all there; the date and price sit on the album row:

```json
{
    "recordType": "track",
    "title": "MG1",
    "artist": "Machine Girl",
    "type": "track",
    "url": "https://machinegirl.bandcamp.com/track/mg1",
    "duration": 46.09,
    "trackNumber": 1,
    "previewUrl": "https://t4.bcbits.com/stream/5da998/mp3-128/3243258131",
    "albumTitle": "WLFGRL+",
    "albumUrl": "https://machinegirl.bandcamp.com/album/wlfgrl",
    "releaseDate": null,
    "priceAmount": null,
    "currency": "USD",
    "tags": ["electronic", "breakcore", "jungle"]
}
```

An album track asked for by its own track URL. It has a price of its own, but no release date apart from the album's:

```json
{
    "recordType": "track",
    "title": "Ghost",
    "artist": "Machine Girl",
    "type": "track",
    "url": "https://machinegirl.bandcamp.com/track/ghost",
    "duration": 185.45,
    "trackNumber": 5,
    "previewUrl": "https://t4.bcbits.com/stream/abc123/mp3-128/456789",
    "albumTitle": "WLFGRL",
    "albumUrl": "https://machinegirl.bandcamp.com/album/wlfgrl",
    "releaseDate": null,
    "priceAmount": 1.0,
    "currency": "USD",
    "tags": ["electronic", "breakcore", "jungle", "New York"]
}
```

A standalone single is a release you can buy in its own right, so it comes back with its own `releaseDate` as well as its `priceAmount`, alongside the album rows in the same run:

```json
{
    "recordType": "track",
    "title": "Head Over Heels",
    "artist": "Casey MQ",
    "type": "track",
    "url": "https://caseymq.bandcamp.com/track/head-over-heels",
    "duration": 232.26,
    "trackNumber": null,
    "previewUrl": "https://t4.bcbits.com/stream/def456/mp3-128/987654",
    "albumTitle": null,
    "albumUrl": null,
    "releaseDate": "2025-07-10T00:00:00Z",
    "priceAmount": 1.0,
    "currency": "USD",
    "tags": ["pop", "Los Angeles"]
}
```

| Field | Type | Description |
|-------|------|-------------|
| `recordType` | string | `"track"` |
| `title` | string | Track title |
| `artist` | string | Artist name |
| `type` | string | Always `"track"` |
| `url` | string | Track URL |
| `duration` | number | Track length in seconds |
| `trackNumber` | number | Position on the album (empty for a standalone single) |
| `previewUrl` | string | Direct 30-second preview MP3 URL (empty when Bandcamp doesn't stream that track) |
| `albumTitle` | string | Parent album title (empty for a standalone single) |
| `albumUrl` | string | Parent album URL (empty for a standalone single) |
| `releaseDate` | string | Release date in ISO 8601 UTC. Filled for a standalone single, which is a release in its own right; empty for any track that belongs to an album, because Bandcamp dates the album, not its tracks |
| `priceAmount` | number | What that track costs to buy on its own, in `currency`. Filled whenever the row came from the track's own page, including an album track you requested by its track URL; empty for tracks returned by **Include Track Listings**, and empty for a free or name-your-price track with no minimum |
| `currency` | string | Price currency inherited from the release |
| `tags` | string\[] | Genre tags inherited from the release |

#### Fan / Supporter (`recordType: "fan"`)

Emitted when Include Supporters is on (one row per supporter of a release, capped at 500 per release) and when you search with Search For set to Fans.

```json
{
    "recordType": "fan",
    "username": "musiclover42",
    "name": "Alex R.",
    "url": "https://bandcamp.com/musiclover42",
    "releaseTitle": "WLFGRL",
    "releaseArtist": "Machine Girl",
    "releaseUrl": "https://machinegirl.bandcamp.com/album/wlfgrl"
}
```

| Field | Type | Description |
|-------|------|-------------|
| `recordType` | string | `"fan"` |
| `username` | string | Fan handle |
| `name` | string | Display name |
| `url` | string | Fan profile URL |
| `releaseTitle` | string | Release the fan supports (empty for fans found via a keyword search, which aren't tied to a release) |
| `releaseArtist` | string | Artist of the supported release (empty for keyword-search fans) |
| `releaseUrl` | string | URL of the supported release (empty for keyword-search fans) |

### Tips for Best Results

- **Start small.** Set `maxResults` to 10–50 on your first run to confirm the data matches your needs, then scale up. A single artist URL can fan out into hundreds of releases.
- **Leave Include Supporters off unless you need fan lists.** Popular releases have thousands of supporters; even capped at 500 per release, fan rows can dominate a large run. Turn it on only when audience data is the goal.
- **Turn off Include Track Listings for a lighter catalog.** When you only need album-level pricing and metadata, switching it off skips per-track rows and keeps runs lean.
- **Use Newest Arrivals for A\&R scouting.** Setting `sortBy` to Newest surfaces fresh releases in a genre — the fastest way to spot rising independent artists before they break.
- **Pair a genre with a location to scout regional scenes.** Discovery accepts a place name like `berlin` or `tokyo` alongside any of the 27 genres, so you can map a city's sound at a glance.
- **Reach for several keywords, not one broad one.** Bandcamp returns at most 50 matches per keyword, so `shoegaze` on its own tops out at 50 no matter how high you set Max Results. Pair it with `dream pop`, `noise pop`, a couple of artist URLs, and a genre discovery in the same run to multiply your reach — all for one start fee, all in one dataset.
- **Filter by `recordType` downstream.** Each run mixes artists, albums, tracks, and fans; split by `recordType` to load each entity into the right table or sheet.

### Pricing

**No compute or time-based charges — you pay per result, plus a small fixed per-run start fee.** Pricing is by record type, so tracks and supporters cost a fraction of full albums and artist profiles. Bronze, Silver, and Gold subscribers pay progressively less; Gold is the everyday advertised price and the discount applies automatically on your account.

| Record type | No discount | Bronze | Silver | Gold |
|-------------|-------------|--------|--------|------|
| Artist / label | $14.40 | $13.55 | $12.75 | **$12.00** |
| Album | $14.40 | $13.55 | $12.75 | **$12.00** |
| Track | $4.80 | $4.50 | $4.25 | **$4.00** |
| Fan / supporter | $2.40 | $2.30 | $2.15 | **$2.00** |

Prices are per 1,000 results of that type. Tracks ride along inside albums and supporters are optional, so you control the mix and the cost.

#### Example Run Costs (Gold pricing)

| What you run | Results produced | Cost |
|--------------|------------------|------|
| 100 albums, no track listings | 100 albums | $1.20 |
| 100 albums + ~10 tracks each | 100 albums + 1,000 tracks | ~$5.20 |
| 1,000 tracks via search | 1,000 tracks | $4.00 |
| 50 artists + full discographies (~20 albums, ~10 tracks each) | 50 artists + 1,000 albums + 10,000 tracks | ~$52.60 |
| 1 popular release + 500 supporters | 1 album + 500 fans | ~$1.01 |

A "result" is any row in the output dataset. Track rows and supporter rows are billed at their own lower per-1,000 rates, so a run that skips track listings or supporters costs less. Platform fees (compute, storage) are additional and depend on your Apify plan.

### Integrations

Export data in JSON, CSV, Excel, XML, or RSS. Connect to 1,500+ apps via:

- **Zapier** / **Make** / **n8n** — Workflow automation
- **Google Sheets** — Direct spreadsheet export
- **Slack** / **Email** — Notifications on new results
- **Webhooks** — Trigger custom APIs on run completion
- **Apify API** — Full programmatic access

### Legal & Ethical Use

This actor is designed for legitimate music market research, catalog analysis, A\&R scouting, and audience intelligence. Users are responsible for complying with applicable laws and Bandcamp's terms of service, including making reasonable-rate requests and respecting copyright and usage rules for any audio, artwork, or text retrieved. Treat fan and supporter data as personal information: do not use it for spam, harassment, or any unlawful purpose. </content> </invoke>

# Actor input Schema

## `startUrls` (type: `array`):

Paste any Bandcamp links. The scraper auto-detects what each one is: an artist or label page (e.g. artistname.bandcamp.com), an album page (/album/...), or a single track (/track/...). For an artist or label page, every release on their discography is collected. (To collect fans, use the Include Supporters option below.)

## `searchTerms` (type: `array`):

Words to look up on Bandcamp, such as an artist name, album title, or genre (e.g. 'lo-fi hip hop' or 'Aphex Twin'). Each keyword returns matching artists, albums, and tracks. Bandcamp returns up to 50 matches per keyword, so add several related keywords when you want a wider sweep. No need to build URLs yourself.

## `searchType` (type: `string`):

Which kind of result your keywords should return. Only applies to Search Keywords above.

## `discoverGenre` (type: `string`):

Browse trending and recommended releases in a music genre, the way Bandcamp's Discover page works. Leave as 'None' to skip genre discovery.

## `discoverLocation` (type: `string`):

Narrow genre discovery to releases tagged from a place, such as 'berlin', 'tokyo', or 'los angeles'. Leave empty for worldwide results. Only applies when a genre is selected above.

## `sortBy` (type: `string`):

How to order genre discovery results.

## `maxResults` (type: `integer`):

Maximum number of results to return across all URLs, searches, and discovery. Set to 0 for unlimited. Each search keyword contributes at most 50 matches (Bandcamp's own limit), so a high number needs artist URLs, more keywords, or genre discovery to fill it. Tip: start with 10-50 to test, then increase.

## `includeTracks` (type: `boolean`):

For each release, also return its full track list with titles, durations, and track numbers, plus a 30-second audio preview link for every track Bandcamp streams. Artists choose which tracks stream, so on some releases only a few tracks carry a preview. Track rows carry the release currency; the price and release date stay on the album row, because a Bandcamp tracklist carries no per-track price or date. Turn off for a lighter dataset with release-level data only.

## `includeFans` (type: `boolean`):

For each release, also return the fans who bought or wishlisted it (their username and profile link). Popular releases can have thousands of supporters, so to keep runs predictable this is capped at 500 supporters per release. Leave off unless you need supporter data.

## Actor input object example

```json
{
  "startUrls": [
    "https://machinegirl.bandcamp.com/"
  ],
  "searchTerms": [],
  "searchType": "all",
  "discoverGenre": "none",
  "sortBy": "top",
  "maxResults": 100,
  "includeTracks": true,
  "includeFans": false
}
```

# Actor output Schema

## `overview` (type: `string`):

Every record from the run in one place — artists, albums, tracks, and fans — distinguished by `recordType`.

## `albums` (type: `string`):

Albums and tracks only, with title, artist, price, ISO 8601 release date, genre tags, artist location, and audio preview links. Albums and standalone singles carry a release date; `priceAmount` is left blank on the name-your-price and free-download releases Bandcamp sells with no fixed price, rather than reporting a number nobody pays — roughly one album in seven overall, and up to a third on some genre and keyword searches, so read an empty price as 'no set price' rather than missing data. A track listed inside an album leaves both the price and the release date blank, because there they belong to the album row; a track reached by its own track URL or a track search hit carries its own price.

## `artists` (type: `string`):

Artist and label profiles only, with name, location, release count, and tags.

## `fans` (type: `string`):

Supporter rows only, linking a fan to the release they bought or wishlisted. Present only when 'Include Supporters' is enabled.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "startUrls": [
        "https://machinegirl.bandcamp.com/"
    ],
    "searchTerms": [],
    "searchType": "all",
    "discoverGenre": "none",
    "discoverLocation": "",
    "sortBy": "top",
    "maxResults": 100,
    "includeTracks": true,
    "includeFans": false
};

// Run the Actor and wait for it to finish
const run = await client.actor("solidcode/bandcamp-music-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "startUrls": ["https://machinegirl.bandcamp.com/"],
    "searchTerms": [],
    "searchType": "all",
    "discoverGenre": "none",
    "discoverLocation": "",
    "sortBy": "top",
    "maxResults": 100,
    "includeTracks": True,
    "includeFans": False,
}

# Run the Actor and wait for it to finish
run = client.actor("solidcode/bandcamp-music-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "startUrls": [
    "https://machinegirl.bandcamp.com/"
  ],
  "searchTerms": [],
  "searchType": "all",
  "discoverGenre": "none",
  "discoverLocation": "",
  "sortBy": "top",
  "maxResults": 100,
  "includeTracks": true,
  "includeFans": false
}' |
apify call solidcode/bandcamp-music-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,solidcode/bandcamp-music-scraper"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/US3jdnjOYc0MYPwek/builds/qe4iK3Hnzdjdtv6Du/openapi.json