Search for a FANZA API or a DMM API in English and you come back empty-handed. The catalog is the biggest one there is, but the front door is locked from outside Japan and the paperwork is all in Japanese. This walks through what actually exists, why none of it works in English, and how to get the same metadata back as normalized JSON.
Does FANZA or DMM have an English API?
No. There’s an affiliate API at affiliate.dmm.com/api, and FANZA (DMM’s adult arm) runs on the same one. Two problems make it useless if you’re not in Japan:
- It’s geo-blocked. dmm.co.jp geo-blocks most of the planet, and the affiliate API sits behind the same wall. You need a Japanese IP just to read the docs for the API that’s meant to send you traffic.
- The docs are Japanese-only. No English reference exists. And the response schema is whatever DMM’s backend looked like in 2014 – dozens of fields, no changelog, no notice when one disappears.
So “FANZA API in English” isn’t a thing you configure. It’s a scraping-and-translation project you’d have to build and then babysit.
Getting DMM/FANZA metadata in English
javinfo runs the geo-block workaround and the normalization once, on the server, and hands you one clean result. Send a DVD code to POST /movie and let the fanza provider answer:
curl -X POST "https://api.javinfo.dev/movie" \ -H "x-javinfo-key: YOUR_KEY" \ -H "Content-Type: application/json" \ -d '{ "q": "SSIS-001", "providers": "fanza" }'{ "q": "SSIS-001", "source": "fanza", "result": { "dvdId": "SSIS-001", "titleEn": "Newcomer NO.1 STYLE ...", "titleJa": "新人 NO.1 STYLE ...", "releaseDate": "2020-07-07", "runtimeMins": 120, "makers": ["S1 NO.1 STYLE"], "actresses": ["Example Actress"], "jacketFullUrl": "https://pics.dmm.co.jp/digital/video/ssis00001/ssis00001pl.jpg" }}You get both titleEn and titleJa, so English is a field you read, not a translation step you own. The dmm/fanza provider returns bilingual metadata – title, cast, maker, label, series, cover art – plus actress profile images and sample gallery URLs that most scrapers skip. Coverage runs to roughly 99% of the dmm.co.jp library, and most codes resolve on the first try.
Need a list instead of a single match? POST /query takes a broad search and returns candidate results in the same shape.
One shape, every source
The result object is the same no matter which provider answers, so the parser you write for FANZA already reads JavDB, MissAV, and javdatabase. That’s the provider-agnostic design the whole thing is built on – one normalized JAV metadata API instead of a separate integration per source.
Sign up at app.javinfo.dev, grab a key, and pass it in the x-javinfo-key header (also on RapidAPI). Billing is usage-based: /movie is $0.0005 per successful result, /query is $0.0002, and failed lookups aren’t charged. New signups get 1,000+ free lookups, no credit card; top up in USDC after that, credited 1:1. No Japanese VPN, no Japanese docs, no scraper to maintain. You can be running in a minute.