Kitsu Python API Docs | dltHub
Build a Kitsu-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
The Kitsu API is a RESTful service for accessing anime data, requiring JWT tokens for authentication, and following JSON:API specification. The base URL is https://kitsu.docs.apiary.io. The REST API base URL is https://kitsu.io/api/edge and Most requests are public GETs; authenticated requests use OAuth2 (Bearer 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 Kitsu data in under 10 minutes.
What data can I load from Kitsu?
Here are some of the endpoints you can load from Kitsu:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| anime | anime | GET | data | List or search anime resources (supports filters, includes, fields, pagination). |
| users | users | GET | data | List or search users; filters include slug, name and self. |
| manga | manga | GET | data | List or search manga resources. |
| library_entries | library-entries | GET | data | User library entries (filters: animeId, userId, status; pagination up to 500). |
| comments | comments | GET | data | List comments (supports filters like postId, parentId). |
| episodes | episodes | GET | data | Episodes for anime (GET supported). |
| auth_token | oauth/token | POST | Obtain OAuth2 access_token (not a GET but essential for auth). |
How do I authenticate with the Kitsu API?
Obtain an OAuth2 access token from https://kitsu.io/api/oauth/token (password or client credentials grant). Send the token in the Authorization header as: Authorization: Bearer <access_token>.
1. Get your credentials
- Create or use an existing Kitsu account.
- Request an access token by POSTing to https://kitsu.io/api/oauth/token with grant_type=password (or another supported grant) and your username and password (application/x-www-form-urlencoded or JSON).
- The successful response includes access_token and token_type = 'bearer'.
- Use the access_token in the Authorization header as "Bearer <access_token>". For refresh, POST the refresh_token to the same endpoint with grant_type=refresh_token; include client_id and client_secret if required.
2. Add them to .dlt/secrets.toml
[sources.kitsu_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 Kitsu 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 kitsu_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline kitsu_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset kitsu_data The duckdb destination used duckdb:/kitsu.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline kitsu_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 anime and users from the Kitsu 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 kitsu_source(access_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://kitsu.io/api/edge", "auth": { "type": "bearer", "access_token": access_token, }, }, "resources": [ {"name": "anime", "endpoint": {"path": "anime", "data_selector": "data"}}, {"name": "users", "endpoint": {"path": "users", "data_selector": "data"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="kitsu_pipeline", destination="duckdb", dataset_name="kitsu_data", ) load_info = pipeline.run(kitsu_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("kitsu_pipeline").dataset() sessions_df = data.anime.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM kitsu_data.anime LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("kitsu_pipeline").dataset() data.anime.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 Kitsu 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 Kitsu?
Request dlt skills, commands, AGENT.md files, and AI-native context.