mdl
An unofficial, fully-typed, sync and async Python client for the private
MyDramaList app API (https://app-api.mydramalist.com/v1), reconstructed from the app's
reverse-engineered spec. Built on curl_cffi and
Pydantic v2.
Install as mydramalist-client; import as mdl.
Interoperability / research tool. This library targets an undocumented, private API discovered by decompiling the MyDramaList Flutter app. Endpoint paths and field names are inferred from machine code and may change without notice; models tolerate unknown/renamed fields but nothing is guaranteed. Use responsibly and in accordance with MyDramaList's Terms of Service. Not affiliated with or endorsed by MyDramaList.
Install
pip install mydramalist-client
The mdl-api-key
Despite its name, mdl-api-key is not a secret — the app fills it with a random 20-char
string generated on each launch, and the server does not validate it. This library generates
a valid one for you, so you do not need to extract or supply anything. You may still pin a
value via api_key= or MDL_API_KEY for reproducible requests, but it is optional. See
docs/api-key-extraction.md.
Heads up — Cloudflare: production sits behind Cloudflare bot protection that fingerprints the client's TLS handshake. A plain
httpx/requestsclient is served a403 "Just a moment..."challenge; only a client impersonating a real mobile/browser TLS fingerprint gets through. See Transport.
Quick start (sync)
from mdl import MDLClient
with MDLClient() as client: # api_key generated automatically
client.auth.login("username", "password") # title & search endpoints need a login
title = client.titles.get_title(686)
print(title.title, title.rating)
results = client.search.titles("signal")
for movie in results:
print(movie.id, movie.title)
Quick start (async)
import asyncio
from mdl import AsyncMDLClient
async def main():
async with AsyncMDLClient() as client:
await client.auth.login("username", "password")
title = await client.titles.get_title(686)
print(title.title)
asyncio.run(main())
Authentication
with MDLClient() as client:
client.auth.login("username", "password") # password is MD5-hashed for you
profile = client.account.get_profile() # bearer token attached automatically
print(profile.username)
Most endpoints need a logged-in client. Since October 2026 the API rejects anonymous
requests to title detail, credits, recommendations, search, explore feeds and every
account/sync endpoint with a bare 400 Bad Request; the client raises
MDLLoginRequiredError (a subclass of MDLAuthError) for these. Genres, tag search,
articles, reviews and public custom lists still work without logging in.
Rejected credentials raise MDLAuthError — the API reports them as 400 "Invalid password or username.", not 401.
Tokens are held in an in-memory store by default. Persist them with FileTokenStore:
from mdl import MDLClient, FileTokenStore
client = MDLClient(token_store=FileTokenStore("~/.mydramalist/token.json"))
The client clears stored tokens on 401 and raises MDLAuthError. Access tokens last
30 days. Automatic token refresh via refresh_token is not yet implemented — callers
must re-authenticate when the access token expires.
Transport
Production MyDramaList sits behind Cloudflare bot protection that fingerprints the
client's TLS/HTTP2 handshake (JA3/JA4). This is the real access gate — not the mdl-api-key.
A plain httpx/requests client (a stock Python TLS stack) is served Cloudflare's
403 "Just a moment..." challenge on every request, regardless of headers or User-Agent.
Only a client that impersonates a real mobile/browser TLS fingerprint is allowed through — in
testing, curl_cffi with impersonate="safari_ios"
(or chrome) reaches the API and returns real JSON.
If you get 403 responses with a "Just a moment..." HTML body, this is why: the request
never reached the API, it was stopped at Cloudflare's edge.
Resource groups
The client exposes one attribute per API area, e.g.:
| Attribute | Area |
|---|---|
client.auth |
login, social auth, register, reset password |
client.account |
own profile/settings, verification, devices, payments |
client.users |
other users & people pages, credits, likes |
client.titles |
title detail, progress, reviews, recommendations, credits, genres |
client.search |
title & people search |
client.explore |
trending / top_airing / upcoming / recommended feeds |
client.reviews |
review CRUD, voting |
client.comments |
comment listing & CRUD |
client.watchlist |
watchlist sync (add/remove/status lists) |
client.custom_lists |
custom lists, items, votes |
client.feeds |
activity feed, posts, embeds, uploads |
client.articles |
articles |
client.friends / client.messages / client.notifications / client.groups |
social |
client.subscription / client.flowers / client.awards / client.reports |
misc |
client.calendar / client.leaderboard |
calendar & leaderboard |
Development
The async implementation under src/mdl/_async is the source of truth; the sync
package src/mdl/_sync is generated from it with
unasync:
pip install -e ".[dev]"
python scripts/build_sync.py # regenerate _sync after editing _async
python scripts/check_sync.py # verify _sync is up to date (CI does this)
ruff check src tests
mypy
pytest
License
MIT
Metadata
Release files for mydramalist-client 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| mydramalist_client-0.2.0.tar.gz | 177.4 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mydramalist_client-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 231.2 kB
Release files / mydramalist_client-0.2.0.tar.gz
| Download URL | mydramalist_client-0.2.0.tar.gz |
|---|---|
| Size | 177.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
de7c703eea401aa060f51bb2943389ad710b57fe5ba326dac6c6a50435ff50dc
|
|
BLAKE2b-256 checksum How to use checksums |
0c0baa3b6ee7668a5f8ac187b92f1cebe77edaa137878fab4595d91fd0636ed0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 10, 2026.
Transparency logRelease files / mydramalist_client-0.2.0-py3-none-any.whl
| Download URL | mydramalist_client-0.2.0-py3-none-any.whl |
|---|---|
| Size | 53.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
10103a2290aca263990381ade5627562d7326292d912dc394fe5c2f0b3dbc182
|
|
BLAKE2b-256 checksum How to use checksums |
57d8c1aaccb084433a838f05752a233f7bb5fd8e7f946bdace8e394d93a26ce3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 10, 2026.
Transparency logSecurity for mydramalist-client 0.2.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for mydramalist_client-0.2.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 10, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.