Pricing
from $3.00 / 1,000 results
Discogs Record Miner
Discogs Record Miner is a dedicated search scraper that extracts artist profiles, releases, and labels from Discogs, so you can build and update your music catalog databases without blocks.
Pricing
from $3.00 / 1,000 results
Rating
0.0
(0)
Developer
Actor stats
0
Bookmarked
2
Total users
1
Monthly active users
24 days ago
Last modified
Categories
Share
Discogs Record Miner is an automated search scraper built to collect artists, releases, master recordings, and labels from Discogs. Music shops, vinyl collectors, and archivists can run multiple search queries in batch mode to pull search result listings in seconds.
The tool includes automatic multi-page pagination to fetch any number of results and routes all requests through a built-in proxy bypass system, so you will not get rate-limited or blocked while collecting data.
Use cases
- Database building: Populate your music application or personal archive with structured Discogs search records.
- Inventory tracking: Match physical music stock lists against the Discogs catalog to pull accurate release links and images.
- Market research: Run search queries for artists and labels to track what releases are currently cataloged.
- Archiving: Save lists of master records and release variations for historical catalog preservation.
Input
The actor accepts a list of queries to run in batch mode. You can filter results by specific category and set a maximum number of records to return for each query:
| Parameter | Type | Default | Description |
|---|---|---|---|
queries | array | ["miles davis"] | List of search queries to run in batch mode (one query per line). Can include artist names, album titles, track names, or catalog numbers. |
searchType | string | all | Filter results by category. Options are all (everything), artist, release, master (master releases), and label. |
maxItemsPerQuery | integer | 25 | Maximum number of search records to return for EACH individual query. The actor automatically paginates through results (25 items per page) to reach this limit. |
requestTimeoutSecs | integer | 30 | Per-request timeout in seconds when calling Discogs search pages. |
Example input
Output
The actor stores results in a dataset. Each entry contains the following fields:
| Field | Type | Description |
|---|---|---|
query | string | The search keyword used to find this record. |
itemType | string | The category of the Discogs item (e.g. artist, release, master release, label). |
itemTitle | string | The name or title of the Discogs item. |
url | string | The direct Discogs link to the item. |
imageUrl | string | The cover image or artist avatar thumbnail URL. |
artistName | string | The creator or artist name (for releases and master records). |
artistUrl | string | The direct Discogs link to the artist's profile. |
scrapedAt | string | The ISO timestamp indicating when the search was completed. |
How it works
- Batch Processing: The actor reads your list of search queries and processes them sequentially.
- Category Filters: Each search is queried with your specific category filter (e.g., searching for "Kind of Blue" as a
releaseonly, or "Miles Davis" as anartistonly). - Automatic Pagination: If you set
maxItemsPerQueryto more than 25, the actor will fetch successive pages (e.g.,page=1,page=2) until the limit is reached or there are no more results. - Proxy Routing: All requests are routed through built-in proxy bypass servers to securely retrieve the content from Discogs.
- Data Compilation: The raw HTML response of each page is parsed to extract metadata for every search card and stored in your Apify dataset.
Integrations
Connect Discogs Record Miner with other apps and services using Apify integrations. You can integrate with Make, Zapier, Slack, Airbyte, GitHub, Google Sheets, Google Drive, and many more. You can also use webhooks to trigger actions whenever results are available.
