Deezer Python API Docs | dltHub
Build a Deezer-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
Deezer is a music streaming platform API providing programmatic access to artists, albums, tracks, charts, playlists, users and search. The REST API base URL is https://api.deezer.com and Public read endpoints are accessible without auth; user-specific endpoints require OAuth access token..
dlt is an open-source Python library that handles authentication, pagination, and schema evolution automatically. dlthub provides AI context files that enable code assistants to generate production-ready pipelines. Install with uv pip install "dlt[workspace]" and start loading Deezer data in under 10 minutes.
What data can I load from Deezer?
Here are some of the endpoints you can load from Deezer:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| tracks | search/track?q={query} | GET | data | Search tracks by query (returns list in 'data') |
| artists | artist/{id} | GET | Get a single artist object | |
| artist_top_tracks | artist/{id}/top | GET | data | Top tracks for an artist (list in 'data') |
| album_tracks | album/{id}/tracks | GET | data | Tracks of an album (list in 'data') |
| chart_tracks | chart/0/tracks | GET | data | Global chart top tracks (list in 'data') |
| playlist_tracks | playlist/{id}/tracks | GET | data | Tracks of a playlist (list in 'data') |
| user_playlists | user/{id}/playlists | GET | data | Playlists for a user (list in 'data') |
| search | search?q={query} | GET | data | Generic search endpoint (returns mixed resources in 'data') |
How do I authenticate with the Deezer API?
Deezer uses OAuth 2.0 for user authentication; create an app in the Deezer Developers dashboard to obtain App ID and Secret, perform the OAuth redirect flow to obtain an access_token. For API calls that require authentication include the access token (access_token) as a query parameter or send as a Bearer token in Authorization header.
1. Get your credentials
- Sign in at https://developers.deezer.com/. 2) Create a new application in your dashboard to get App ID (app_id) and App Secret (secret). 3) Implement the OAuth redirect flow: request user authorization at https://connect.deezer.com/oauth/auth.php?app_id={app_id}&redirect_uri={redirect_uri}&perms={perms} then exchange code for access_token via https://connect.deezer.com/oauth/access_token.php?app_id={app_id}&secret={secret}&code={code}.
2. Add them to .dlt/secrets.toml
[sources.deezer_source] app_id = "your_app_id" app_secret = "your_app_secret" access_token = "your_oauth_access_token"
dlt reads this automatically at runtime — never hardcode tokens in your pipeline script. For production environments, see setting up credentials with dlt for environment variable and vault-based options.
How do I set up and run the pipeline?
Set up a virtual environment and install dlt:
uv venv && source .venv/bin/activate uv pip install "dlt[workspace]"
1. Install the dlt AI Workbench:
dlt ai init --agent <your-agent> # <agent>: claude | cursor | codex
This installs project rules, a secrets management skill, appropriate ignore files, and configures the dlt MCP server for your agent. Learn more →
2. Install the rest-api-pipeline toolkit:
dlt ai toolkit rest-api-pipeline install
This loads the skills and context about dlt the agent uses to build the pipeline iteratively, efficiently, and safely. The agent uses MCP tools to inspect credentials — it never needs to read your secrets.toml directly. Learn more →
3. Start LLM-assisted coding:
Use /find-source to load data from the Deezer API into DuckDB.
The rest-api-pipeline toolkit takes over from here — it reads relevant API documentation, presents you with options for which endpoints to load, and follows a structured workflow to scaffold, debug, and validate the pipeline step by step.
4. Run the pipeline:
python deezer_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline deezer_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset deezer_data The duckdb destination used duckdb:/deezer.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline deezer_pipeline show
This opens the Pipeline Dashboard where you can verify pipeline state, load metrics, schema (tables, columns, types), and query the loaded data directly.
Python pipeline example
This example loads tracks and artists from the Deezer API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:
import dlt from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources @dlt.source def deezer_source(access_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.deezer.com", "auth": { "type": "bearer", "access_token": access_token, }, }, "resources": [ {"name": "tracks", "endpoint": {"path": "search/track?q={query}", "data_selector": "data"}}, {"name": "artists", "endpoint": {"path": "artist/{artist_id}"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="deezer_pipeline", destination="duckdb", dataset_name="deezer_data", ) load_info = pipeline.run(deezer_source()) print(load_info)
To add more endpoints, append entries from the resource table to the "resources" list using the same name, path, and data_selector pattern.
How do I query the loaded data?
Once the pipeline runs, dlt creates one table per resource. You can query with Python or SQL.
Python (pandas DataFrame):
import dlt data = dlt.pipeline("deezer_pipeline").dataset() sessions_df = data.tracks.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM deezer_data.tracks LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("deezer_pipeline").dataset() data.tracks.df().head()
See how to explore your data in marimo Notebooks and how to query your data in Python with dataset.
What destinations can I load Deezer data to?
dlt supports loading into any of these destinations — only the destination parameter changes:
| Destination | Example value |
|---|---|
| DuckDB (local, default) | "duckdb" |
| PostgreSQL | "postgres" |
| BigQuery | "bigquery" |
| Snowflake | "snowflake" |
| Redshift | "redshift" |
| Databricks | "databricks" |
| Filesystem (S3, GCS, Azure) | "filesystem" |
Change the destination in dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. See the full destinations list.
Troubleshooting
Authentication failures
If a request to a user-specific endpoint returns a 401 or an error with an "error" object indicating invalid token, verify your OAuth token is not expired and that it was obtained with correct app_id/secret and scopes. Refresh token by re-running OAuth flow.
Pagination and data selection
Most list endpoints return paginated responses with the list under the "data" key and a "next" URL for the next page. Example keys to inspect: data, total, next, index, limit. To retrieve all records follow the "next" URL until absent.
Rate limits and throttling
Deezer does not publish strict per-user rate limits; if you receive server errors or throttling-like responses, implement exponential backoff and respect "next" pagination rather than requesting large ranges in parallel.
Ensure that the API key is valid to avoid 401 Unauthorized errors. Also, verify endpoint paths and parameters to avoid 404 Not Found errors.
Next steps
Continue your data engineering journey with the other toolkits of the dltHub AI Workbench:
data-exploration— Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.dlthub-runtime— Deploy, schedule, and monitor your pipeline in production.
dlt ai toolkit data-exploration install dlt ai toolkit dlthub-runtime install
Was this page helpful?
Community Hub
Need more dlt context for Deezer?
Request dlt skills, commands, AGENT.md files, and AI-native context.