javdatabase.com is one of the better places to read about a release – proper English descriptions, curated sample galleries, the occasional trailer. It’s also a site built for browsing, not a database you can call. There’s no public javdatabase API. If you want that data in an app, your only options are opening a browser tab or writing a scraper. javinfo gives you a third one.
The data, without the site
javinfo runs javdatabase as a provider. Hit POST /movie with providers: "javdatabase" and you get the fields the site is good at – a full English description (not a one-line blurb), sampleImages, and a trailerUrl when one exists – on top of the standard base fields: title, cast, release date, cover art.
curl -X POST "https://api.javinfo.dev/movie" \ -H "x-javinfo-key: YOUR_KEY" \ -H "Content-Type: application/json" \ -d '{ "q": "SSIS-001", "providers": "javdatabase" }'{ "q": "SSIS-001", "source": "javdatabase", "result": { "dvdId": "SSIS-001", "titleEn": "After Abstaining From Sex...", "extra": { "description": "A newlywed wife succumbs to temptation...", "sampleImages": ["https://www.javdatabase.com/images/samples/ssis-001_1.webp"], "trailerUrl": "https://www.javdatabase.com/trailers/ssis-001.mp4" } }}Why not just scrape javdatabase.com
Because a scraper is a maintenance liability, not an integration. You’d be parsing HTML that changes without a changelog, fighting whatever anti-bot the site adds next, and rebuilding your parser the morning it silently returns blanks. javinfo does that work once, server-side, and hands you a stable JSON contract instead. When the markup moves, we fix it; your code keeps calling the same endpoint.
One shape, every source
The /movie endpoint speaks to all four providers – dmm/fanza, javdb, missav, javdatabase – and returns one normalized result no matter which answered. So the descriptions and samples from javdatabase sit in the same shape as JavDB’s magnet links and MissAV’s streams. Pin "providers": "javdatabase" or let the default order try it and take javdatabase whenever it has the best answer. It’s one JAV metadata API over every source, provider-agnostic by design – the same queryable database angle, just pinned to one provider.
Sign up at app.javinfo.dev, grab a key, and pass it in the x-javinfo-key header (also on RapidAPI). Usage-based billing: /movie is $0.00075 per successful result, /query is $0.00035, failed lookups free. New signups get 50 free lookups, no credit card. (The old /search endpoint that did two jobs at once is being replaced – read about the endpoint split.) You can be running in a minute.