MyDramaList Python API Docs | dltHub

Build a MyDramaList-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.

Last updated:

MyDramaList provides an API for accessing information about titles, people, and watchlists in their database. The REST API base URL is https://api.mydramalist.com/v1 and all requests require an 'mdl-api-key' header, and authenticated requests require an 'Authorization' bearer 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 add "dlt[hub]" and start loading MyDramaList data in under 10 minutes.


What data can I load from MyDramaList?

Here are some of the endpoints you can load from MyDramaList:

ResourceEndpointMethodData selectorDescription
titlestitles/[ID]GETGet information for a specific title
title_ratingstitles/[ID]/ratingsGETGet ratings for a title
title_creditstitles/[ID]/creditsGETGet credits for a title
title_reviewstitles/[ID]/reviewsGETGet reviews for a title
person_detailspeople/[ID]GETGet details for a person
person_creditspeople/[ID]/creditsGETGet credits for a person
title_updatestitles/updates/[START_DATE]GETGet recently updated titles

How do I authenticate with the MyDramaList API?

MyDramaList uses an API key provided in the 'mdl-api-key' header for general access, and an 'Authorization' header with a 'Bearer' token for authenticated user-specific actions.

1. Get your credentials

MyDramaList currently does not provide public access to its REST API. While there is a documentation page for a v1 API, official access to API credentials is restricted to private partners and is not available via a self-service developer dashboard. Requests for access are generally declined. Users looking to integrate with MyDramaList typically rely on unofficial, community-maintained clients that handle the necessary authentication/fingerprinting bypasses.

2. Add them to .dlt/secrets.toml

[sources.mydramalist_source] # Note: Public API keys are not currently issued. If using an unofficial client or # if access is granted in the future, the following header is historically required: mdl_api_key = "your_client_id_here" mdl_bearer_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 init uv add "dlt[hub]"

1. Install the dlt AI harness:

uv run dlthub 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:

uv run dlthub ai toolkit install rest-api-pipeline

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 MyDramaList 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:

uv run python mydramalist_pipeline.py

If everything is configured correctly, you'll see output like this:

Pipeline mydramalist_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset mydramalist_data The duckdb destination used duckdb:/mydramalist.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs

Inspect your pipeline and data:

uv run dlthub 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 /v1/search/titles and /v1/oauth/token from the MyDramaList 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 mydramalist_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.mydramalist.com/v1", "auth": {"type": "bearer", "token": api_key}, }, "resources": [ {"name": "titles", "endpoint": {"path": "titles/{id}"}}, {"name": "person_details", "endpoint": {"path": "people/{id}"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="mydramalist_pipeline", destination="duckdb", dataset_name="mydramalist_data", ) load_info = pipeline.run(mydramalist_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("mydramalist_pipeline").dataset() sessions_df = data.titles.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM mydramalist_data.titles LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("mydramalist_pipeline").dataset() data.titles.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 MyDramaList data to?

dlt supports loading into any of these destinations — only the destination parameter changes:

DestinationExample 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 harness:

  • data-exploration — Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.
  • dlthub-platform — Deploy, schedule, and monitor your pipeline in production.
uv run dlthub ai toolkit install data-exploration uv run dlthub ai toolkit install dlthub-platform

Was this page helpful?

Community Hub

Need more dlt context for MyDramaList?

Request dlt skills, commands, AGENT.md files, and AI-native context.

Available Pipelines