Every JAV Site, One API: Javinfo on RapidAPI

You want metadata for a DVD code. You find a site, write a parser, and ship. The site changes its HTML and the parser dies. You add a second source to cover the gaps, then a third. A year later you maintain five integrations to get a title, a release date, and a cover image.

Javinfo is one endpoint that queries the major catalog sources and returns the same JSON shape whichever one answered. You send a code. You get normalized metadata. We run the scraping, the Cloudflare challenges, and the region blocks.

No key to manage

RapidAPI signs the upstream call for you. You send your RapidAPI key and host, and that is the whole setup. There is no javinfo key to create, rotate, or leak.

curl -X POST 'https://javinfo.p.rapidapi.com/movie' \
  -H 'Content-Type: application/json' \
  -H 'X-RapidAPI-Key: YOUR_RAPIDAPI_KEY' \
  -H 'X-RapidAPI-Host: javinfo.p.rapidapi.com' \
  -d '{ "q": "SSIS-001" }'

{
  "q": "SSIS-001",
  "source": "fanza",
  "result": {
    "contentId": "ssis00001",
    "dvdId": "SSIS-001",
    "titleEn": "Newcomer NO.1 STYLE ...",
    "titleJa": "新人NO.1 STYLE ...",
    "runtimeMins": 120,
    "releaseDate": "2020-07-07",
    "makers": ["S1 NO.1 STYLE"],
    "actresses": ["Example Actress"],
    "jacketFullUrl": "https://pics.dmm.co.jp/digital/video/ssis00001/ssis00001pl.jpg"
  }
}

Every source maps onto that same object. You read result.dvdId and result.titleEn the same way whichever source produced them. Anything a single source knows and the others do not sits under result.extra, so the shared shape stays stable.

Three endpoints cover most work

/movie returns one best match from a code, a title, or a performer name. Reach for it when you know what you want.

/query returns a list of matches. Start here when you only have a keyword, an actress name, or part of a title, then send the code you picked to /movie. It accepts filters for genre, actress, maker, series, runtime, and release window, plus paging up to 50 results.

/idols searches performers instead of titles. One merged performer catalog covers both sources we build it from, so a single query returns name, image, age, height, and aliases. Pass an id from the list to /idols/{id} for one performer.

/random serves bulk random cards for a landing page, and /health answers without auth for uptime monitors.

What comes back when there is no match

A miss on /movie returns 404. /query and /idols return 200 with count: 0 and an empty array, which is the shape your pagination code already handles. Read the status before you branch: an empty result and a failed request are different outcomes and you handle them differently.

Reading your own quota

Two of our headers ride along on every response: X-Cache tells you HIT or MISS, and X-Response-Time-Ms gives server-side latency. A repeat of the same query and source comes back as a hit, so it answers fast.

RapidAPI adds the quota headers:

Read those instead of estimating from your own request counter, which drifts the moment you retry anything.

Every plan has a hard limit

Every tier returns the same fields. Only the limits differ.

Each plan carries a hard limit. A runaway loop on a metered API produces an overage bill, and RapidAPI cannot waive one without the provider’s explicit permission. Their own documentation says so. We set the hard limit on all four tiers, so the worst case is a 429 and a paused script.

Get half the marketplace fee back

RapidAPI takes 25% of your plan price as a marketplace fee. We hand half of that back.

Link your RapidAPI account from app.javinfo.dev and you keep the same request allotment, plus 12.5% of your plan price credited as in-app balance every month. On Pro that runs about $1.25 a month, which spends on any endpoint at normal rates. Link once and it applies while your subscription stays active.

You also get the direct endpoint. Calls to api.javinfo.dev skip the marketplace hop, and we treat your monthly cap as a soft ceiling: past it we serve the call and charge it at standard credit rates instead of blocking you.

What the marketplace adds, and what it costs

RapidAPI gives you onboarding in minutes, key management, usage dashboards, and one bill for every API you subscribe to. You pay 25% for that, and your traffic takes an extra hop through their gateway.

The direct API answers faster and bills at our own rates. You hold a key and top up with crypto.

Picking a path

Testing a project, or you want one dashboard and one invoice for everything you call? Take the free Basic plan on RapidAPI and upgrade when the volume justifies it.

For production traffic or the lowest latency, grab a key at app.javinfo.dev.

Already paying for a RapidAPI plan? Link it. You keep your request allotment, collect the 12.5% back, and can call the direct endpoint the same day.

FAQ

Do I need a javinfo account to use the RapidAPI listing? No. Your RapidAPI key is enough. An account at app.javinfo.dev is only for the direct API and for the credit-back.

What happens when I hit my monthly cap? You get 429 responses until the period resets. The hard limit means no overage charges, so you will not receive a surprise invoice.

What does a request with no match return? A 404 on /movie, /random, or /idols/{id}. /query and /idols return 200 with count: 0 and an empty array.

Can I pick which source answers? Yes. Pass providers on /movie or /query to force a specific one. Same q and providers twice hits our cache.

Is there a free tier? Basic costs $0 and allows 100 requests a month at 10 per minute. It returns the same data as the paid tiers, so you can build and test against it.

Does the API host or stream video? No. Javinfo indexes metadata only.

Start on RapidAPI with the free plan, or read the full endpoint reference. For how the direct API compares, see the dashboard walkthrough. Javinfo is a single JAV metadata API covering the sources you would otherwise scrape one at a time.