AniList Python API Docs | dltHub
Build a AniList-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
AniList API provides documentation for user, media list, and studio objects. The API filters media by various IDs and popularity. Essential query filters include media IDs and popularity ranges. The REST API base URL is https://graphql.anilist.co and all requests requiring auth use an OAuth2 access token supplied as Authorization: Bearer .
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 AniList data in under 10 minutes.
What data can I load from AniList?
Here are some of the endpoints you can load from AniList:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| media | graphql | POST | data.media | Query media by id or search; returns Media object(s) under the field name used in the query (commonly "media"). |
| user | graphql | POST | data.User | Query user by id or name; returned under the query field (e.g. "User"). |
| media_list | graphql | POST | data.MediaListCollection / data.MediaList | User media lists and collections (fields returned under the query field names). |
| studio | graphql | POST | data.Studio | Query studio by id; result available under the query field name. |
| page | graphql | POST | data.Page | Generic paginated results (Page connection) returned under the query field name (e.g. "Page"). |
How do I authenticate with the AniList API?
AniList uses OAuth2 access tokens. Authenticated requests include an Authorization: Bearer <access_token> header.
1. Get your credentials
- Sign in to AniList and open Developer Settings: https://anilist.co/settings/developer
- Click “Create New Application”, fill in name and redirect URL.
- Choose Authorization Code Grant (server) or Implicit Grant (client) and follow the OAuth flow to obtain an access token.
- The token returned can be used as the Bearer token in API requests. Tokens are long‑lived (≈1 year).
2. Add them to .dlt/secrets.toml
[sources.anilist_source] access_token = "your_access_token_here"
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 AniList 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 anilist_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline anilist_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset anilist_data The duckdb destination used duckdb:/anilist.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline anilist_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 media and user from the AniList 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 anilist_source(access_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://graphql.anilist.co", "auth": { "type": "bearer", "access_token": access_token, }, }, "resources": [ {"name": "media", "endpoint": {"path": "graphql", "data_selector": "data.media"}}, {"name": "user", "endpoint": {"path": "graphql", "data_selector": "data.User"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="anilist_pipeline", destination="duckdb", dataset_name="anilist_data", ) load_info = pipeline.run(anilist_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("anilist_pipeline").dataset() sessions_df = data.media.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM anilist_data.media LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("anilist_pipeline").dataset() data.media.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 AniList 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.
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 AniList?
Request dlt skills, commands, AGENT.md files, and AI-native context.