1001Tracklists API1001tracklists.com ↗
Access DJ set tracklists, chart rankings, artist profiles, and track metadata from 1001tracklists.com via 13 structured endpoints.
What is the 1001Tracklists API?
The 1001tracklists.com API exposes 13 endpoints covering DJ set tracklists, chart rankings, artist profiles, and individual track metadata. The get_tracklist endpoint returns a full ordered track listing — including artist, title, label, remix info, and streaming links — for any tracklist page URL. You can also browse the latest sets, search by title or DJ name, look up chart data across weekly/trending/most-heard categories, and fetch multiple tracklists in a single batch call.
curl -X GET 'https://api.parse.bot/scraper/b93889bc-63b3-4524-8ff6-be513ab4401a/get_tracklist?url=https%3A%2F%2Fwww.1001tracklists.com%2Ftracklist%2Fbvq54h9%2Fskrillex-mainstage-sziget-festival-hungary-2026-08-15.html' \ -H 'X-API-Key: $PARSE_API_KEY'
Get detailed tracklist from a 1001tracklists URL. Returns event metadata (name, date, lineup) and individual track details including artist, title, label, mix information, cue times, and streaming links. Requires a full tracklist page URL.
| Param | Type | Description |
|---|---|---|
| urlrequired | string | The full URL of a tracklist page on 1001tracklists.com (e.g. https://www.1001tracklists.com/tracklist/2hsp3419/hardwell-hardwell-on-air-532-2026-06-05.html) |
{
"type": "object",
"fields": {
"url": "string, the tracklist page URL",
"event": "object containing name (string), date (string, optional), and lineup (array of artist name strings)",
"tracks": "array of track objects with artist, title, label, mix, links, cue_seconds (integer or null, timecode in seconds within the set), and order"
},
"sample": {
"data": {
"url": "https://www.1001tracklists.com/tracklist/2hsp3419/hardwell-hardwell-on-air-532-2026-06-05.html",
"event": {
"name": "Hardwell-Hardwell On Air532 2026-06-05",
"lineup": []
},
"tracks": [
{
"label": "REVEALED",
"links": {},
"order": 1,
"title": "Hardwell & Showtek - How We Do (NLW Remix)",
"artist": "Hardwell & Showtek"
}
]
},
"status": "success"
}
}About the 1001Tracklists API
Tracklist and Track Data
The core get_tracklist endpoint accepts a 1001tracklists.com tracklist page URL and returns an event object (name, date, lineup) alongside a tracks array. Each track object includes artist, title, label, mix (remix/edit name), links to streaming platforms, and order within the set. The get_track endpoint goes further for individual track pages, returning genre, release_date, and total_plays — the total number of tracklist appearances across the entire site.
Browsing and Discovery
list_latest paginates recent tracklists with optional date range filtering via date_from and date_to, and an include_tracks flag that expands each summary into a full tracklist. list_homepage_sets and list_homepage_sets_light pull directly from the homepage feed in site order; the light variant returns only title, url, date, and genres without fetching detail pages, keeping call costs low. list_recent_sets takes a required date window (date_from, date_to) and paginates until coverage is proven complete, returning a coverage_complete boolean alongside pages_scraped and oldest_date_seen. list_genre_sets filters by a hyphenated genre slug like progressive-house or afro-house.
Charts and Artist Profiles
list_charts returns ranked tracks for weekly, trending, and mostheard chart types, each item providing a name (artist – title format) and its 1001tracklists track URL. get_artist accepts either a DJ name string or an artist page URL and returns an artist object with track_count, tracklist_count, and country, plus a top_tracks array sorted by plays descending and a tracklists array of recent sets.
Search and Batch
search_tracklists takes a title string and an optional uploader (DJ name) to return up to 10 matching tracklist pages with url, title, and djName. find_by_media_url resolves a SoundCloud or YouTube URL to the corresponding 1001tracklists page, returning the full tracklist object when found or {"found": false} otherwise. get_tracklists_batch accepts a JSON array of tracklist URLs and returns all results in a single response, each in the same shape as get_tracklist.
The 1001Tracklists API is a managed, monitored endpoint for 1001tracklists.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when 1001tracklists.com changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official 1001tracklists.com API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Identify every track in a DJ set by feeding a 1001tracklists URL to
get_tracklistand reading the orderedtracksarray. - Monitor which tracks are currently trending in electronic music using
list_chartswith themostheardortrendingchart type. - Build a DJ discography page by calling
get_artistand reading thetracklistsandtop_tracksarrays. - Cross-reference a YouTube or SoundCloud mix URL against tracklist data using
find_by_media_urlto retrieve set metadata. - Collect all techno or progressive-house sets within a date window using
list_genre_setswithlist_recent_setsfor complete coverage. - Enrich a music database with play-count and label data by calling
get_trackfor each track URL returned in chart or tracklist results. - Batch-ingest multiple DJ sets in one call using
get_tracklists_batchto avoid multiple sequential requests.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 200 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
| Team | $300/mo | 20,000 | 300 req/min |
| Company | $1,000/mo | 100,000 | 500 req/min |
Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does 1001tracklists.com have an official developer API?+
What does `list_recent_sets` return that `list_latest` does not?+
list_recent_sets requires explicit date_from and date_to parameters and internally paginates until it can confirm full coverage of that window, exposing a coverage_complete boolean and pages_scraped count. Each item also includes a set_id field and dj_name. list_latest supports optional date filtering but does not guarantee coverage completeness — it returns up to 30 items per page with no coverage signal.How does genre filtering work across the listing endpoints?+
list_genre_sets requires a hyphenated lowercase genre slug (e.g. tech-house, afro-house). list_homepage_sets and list_recent_sets accept a genre string and match it as a case-insensitive substring against each set's genre tags. list_homepage_sets_light adds a genre_exact boolean that, when true, requires an exact case-insensitive match against individual tags rather than a substring match.Does the API return listener counts, follower counts, or social stats for DJs?+
get_artist returns track_count, tracklist_count, and country from the artist's 1001tracklists profile, but social follower counts or streaming platform listener numbers are not included. You can fork this API on Parse and revise it to add an endpoint pulling from external platform profiles if that data is needed.Are there limitations on how far back historical tracklist data goes?+
list_mixes paginates through yearly archives with 34 pages per year, going backwards in time from the current year — so coverage depth depends on how far back 1001tracklists.com's own archive extends. Very old or incomplete entries may have null date or dj_name fields. The list_recent_sets endpoint's coverage_complete flag tells you whether the crawl fully covered your requested date window.