API Documentation

Introduction

Drop a single <iframe> into your own site and get a fully working AniKino player back - no API key, no sign-up. Every embed resolves the real stream server-side and serves it through AniKino's own Plyr-based player, not a nested third-party iframe - the actual provider CDN URL is never exposed to your page or your visitors.

<iframe
  src="https://your-domain.example/embed/movie/{id}"
  width="100%" height="560"
  frameborder="0" allowfullscreen
></iframe>

<iframe
  src="https://your-domain.example/embed/tv/{id}/{season}/{episode}"
  width="100%" height="560"
  frameborder="0" allowfullscreen
></iframe>

<iframe
  src="https://your-domain.example/embed/anime/{id}/{episode}?season=1&audio=dub"
  width="100%" height="560"
  frameborder="0" allowfullscreen
></iframe>

Providers

Each embed type has its own default source and an alternate you can force with ?server=. Anime and Movie/TV don't share providers - the same server=ru value means a different backend depending on which embed you're calling, both labeled RU MV on the frontend since they're both "the Russian-dub source" for their respective content type.

The dot on each card below is that provider's live status - checked server-side on a timer against a fixed, known-good title (not on page load), so it reflects whether the provider itself is actually reachable right now, not just this browser's own network. The line under it shows the hourly speed scan: how long resolving took, time to the first video chunk, download speed measured from our server, and whether the video comes straight from the provider's CDN to you (direct) or through our server (relay).

Movie Embed

Embed a movie player. Resolves through Kino (default), T1M, or RU MV.

<iframe src="https://your-domain.example/embed/movie/{id}" width="100%" height="560" allowfullscreen></iframe>

# Deadpool 2, default (Kino)/embed/movie/293660# same movie, by IMDB id/embed/movie/tt4425200# forced T1M/embed/movie/293660?server=t1m# forced RU MV/embed/movie/293660?server=ru# autoplay on load, resume from 2 minutes in/embed/movie/293660?autoplay=1&startAt=120

TV Show Embed

Embed a specific episode. Resolves through Kino (default), T1M, or RU MV.

<iframe src="https://your-domain.example/embed/tv/{id}/{season}/{episode}" width="100%" height="560" allowfullscreen></iframe>

# Breaking Bad S1E1, default (Kino)/embed/tv/1396/1/1# forced T1M/embed/tv/1396/1/1?server=t1m# forced RU MV/embed/tv/1396/1/1?server=ru# binge mode - autoplay + auto-advance to S1E2, S1E3... on end/embed/tv/1396/1/1?autoplay=1&autonext=1

Anime Embed

Embed an anime episode with sub/dub selection, resolved through MVP (default), KaF, Neko, or RU MV.

<iframe src="https://your-domain.example/embed/anime/{id}/{episode}?season=1&audio=dub" width="100%" height="560" allowfullscreen></iframe>

# Bleach S1E1, dub, default (MVP)/embed/anime/30984/1?season=1&audio=dub# Sub, season 2, forced KaF/embed/anime/30984/1?season=2&server=kaa# Dub, Neko (falls back to MVP automatically if unavailable)/embed/anime/30984/1?audio=dub&server=neko# RU MV - only succeeds when we have a confident title match/embed/anime/30984/1?server=ru# binge mode - autoplay + auto-advance to episode 2, 3... on end/embed/anime/30984/1?audio=dub&autoplay=1&autonext=1# same show, by MAL id instead of TMDB id/embed/anime/mal-269/1?audio=dub# same show, by AniList id (anilist- and al- both work)/embed/anime/anilist-269/1?audio=dub

Query Parameters

Parameters supported today, plus what's still planned.

Episode Release Progress

How many episodes of a season we've actually got cached (sub/dub/RU-dub counts), whether the season is finished, and an upcoming air date when we have one. Read-only, rate limited to 40 requests/minute per IP (separate from every other limiter on this page).

fetch('https://your-domain.example/api/public/episode-progress?tmdbId=30984&season=4')
  .then(function (r) { return r.json(); })
  .then(function (data) { console.log(data); });

# Bleach, season 4/api/public/episode-progress?tmdbId=30984&season=4# by title instead of tmdbId/api/public/episode-progress?title=Bleach

{
  "ok": true,
  "found": true,
  "data": {
    "tmdbId": 30984,
    "season": 4,
    "title": "Bleach",
    "subEpisodes": 28,
    "dubEpisodes": 28,
    "totalEpisodes": 28,
    "ruDubEpisodes": 28,
    "isFinished": true,
    "tmdbSeasonEpisodeCount": 28,
    "upcomingDate": null,
    "source": "anikoto+native",
    "cachedAt": 1767225600000
  }
}

found: false (with an ok: true, 200) means we don't have this title/season cached yet - not an error, just nothing to report. A genuinely malformed request (neither tmdbId nor title given) returns 400.

Anime TMDB Mapping

Every other anime embed API out there is built around MAL or AniList ids - we're the outlier keying everything off TMDB (see the callout on Anime Embed). This translates between them: hand it a TMDB id we've already mapped and get back its MAL/AniList id, or the reverse via title. Same 40 requests/minute per IP limit as Episode Release Progress, read-only.

fetch('https://your-domain.example/api/public/tmdb-mapping?tmdbId=30984')
  .then(function (r) { return r.json(); })
  .then(function (data) { console.log(data); });

# Bleach/api/public/tmdb-mapping?tmdbId=30984# by title instead of tmdbId/api/public/tmdb-mapping?title=Bleach

{
  "ok": true,
  "found": true,
  "data": {
    "tmdbId": 30984,
    "malId": 269,
    "anilistId": 269,
    "title": "Bleach",
    "cachedAt": 1767225600000,
    "validatedAt": 1767225600000
  }
}

We only have a mapping cached for a title once something on the site has actually resolved it before - this isn't a full TMDB↔MAL/AniList directory, just our own cache. found: false means we don't have it yet.

Security

The raw upstream stream URL is never exposed anywhere - not in the page source, not in a JSON response, not at any layer of a nested playlist. Every embed resolves the real stream server-side and hands the player a session-bound, encrypted, expiring proxy URL instead - only /api/m3u8-proxy ever talks to the real CDN, and only for the exact browser session that resolved it. Copying a resolved stream URL out of your browser's network tab and loading it in a different browser/session returns 403 This link does not belong to your session - verified live.

Player Events

The embedded player posts postMessage events to the parent window at every play, pause, seek-ready, and end, plus a throttled position update (at most once every 5 seconds) while playing - so your page can track playback state without ever reaching into the iframe (which same-origin policy blocks anyway).

window.addEventListener('message', function (e) {
  if (!e.data || e.data.source !== 'anikino-embed') return;
  // e.data.event: 'ready' | 'play' | 'pause' | 'timeupdate' | 'ended' | 'autonext'
  // e.data.currentTime / e.data.duration: seconds (floats)
  // 'autonext' also carries e.data.nextEpisodeUrl - fired right before the iframe
  // navigates itself there (only when ?autonext=1 was set - see Query Parameters)
  console.log(e.data.event, e.data.currentTime, e.data.duration);
});

Resume Playback

Save and restore a viewer's watch position using the timeupdate event above and the startAt query parameter - same idea as VidSrc's resume flow. Listen for timeupdate, store currentTime against that title/episode in your own backend or localStorage, then next time build the iframe src with ?startAt=<seconds> and the player seeks there as soon as its metadata loads - no extra round trip needed.

var lastKnownPosition = 0;
window.addEventListener('message', function (e) {
  if (!e.data || e.data.source !== 'anikino-embed') return;
  if (e.data.event === 'timeupdate' || e.data.event === 'pause') {
    lastKnownPosition = e.data.currentTime;
    localStorage.setItem('resume:293660', lastKnownPosition);
  }
});

// next visit - resume where they left off
var resumeAt = localStorage.getItem('resume:293660') || 0;
iframe.src = '/embed/movie/293660?startAt=' + resumeAt;

Captions Settings

Every player - /embed/* and the main site's own player alike - has a Captions Settings entry under the gear icon's Settings menu, right below Captions. It's there because different providers ship separately-timed rips of the same episode, so a caption borrowed from a different provider than the one actually serving the video can drift out of sync by a few real seconds - not something fixable at the source, so the viewer gets a manual nudge instead.

Saved to the viewer's own localStorage, per device - not sent to us, and not something a host page can read or set through the embed API. Sync Offset works by directly shifting the loaded caption track's cue timing (not the video), so it applies instantly with no reload, and persists across episode/server switches until changed again.

Test Your Embed

Questions & Support

Got a question about the embed API, found a bug, or want a title added or fixed? Send it here.

Last Updated

This page and the embed API were last updated August 26, 2026.