Endpoints
// Movie
GET https://mail.videasy.xyz/embed/movie/{TMDB_ID}
// TV episode
GET https://mail.videasy.xyz/embed/tv/{TMDB_ID}/{SEASON}/{EPISODE}
// TV, query form (also supported by this build)
GET https://mail.videasy.xyz/embed/tv/{TMDB_ID}?s={SEASON}&e={EPISODE}
These are the real routes in this build's .htaccess and player.php. They are iframe endpoints, not JSON endpoints: the response is the player itself, so you embed the URL directly instead of fetching JSON and then building a second player.
Integration example
<iframe
src="https://mail.videasy.xyz/embed/movie/533535"
width="100%" height="100%"
frameborder="0" allowfullscreen>
</iframe>Why this works as the Videasy API
- Same ID system: TMDB IDs, so existing Videasy-style code that already stores TMDB IDs needs no remapping.
- No auth in the URL: no key to leak in page source, rotate, or expire.
- Predictable URLs: movie, TV, season and episode are all in the path, so URLs can be built in any language or framework.
- Subtitles included: the player handles subtitles, so the API page does not need a separate subtitle integration step.
Migration checklist
1. Find every Videasy base URL in your code. 2. Replace it with the Videasy embed base URL above. 3. Keep every TMDB ID, season and episode number unchanged. 4. Test one movie and one TV episode before deploying the change everywhere. See also the Videasy player and the Videasy hub.
Videasy API in depth
The Videasy API is a URL pattern, not a JSON service
That distinction matters, because many people searching for a videasy API expect a JSON API with an endpoint that returns data. The Videasy API on this site is different: it is an embed API. You build a URL from a TMDB ID, put that URL in an iframe, and the response is the player itself. There is no JSON to parse, no SDK to install, and no API key to put in a header.
That simplicity is the point. A JSON API would need a second step — fetch data, then build a player from it — and a key that could leak in page source. A URL-based embed API skips both steps. The trade-off is also clear: if you need metadata like titles, posters, cast lists or ratings, this API does not return them. You get that metadata from TMDB itself, and you use the Videasy API only for playback.
Videasy API endpoints, explained
Movie endpoint
/embed/movie/{TMDB_ID} — one number, one film. Replace the placeholder with the TMDB movie ID and the iframe plays that movie.
TV episode endpoint
/embed/tv/{TMDB_ID}/{SEASON}/{EPISODE} — three numbers, one exact episode. Change the season or episode number and the same page template plays a different episode.
TV query form
/embed/tv/{TMDB_ID}?s={SEASON}&e={EPISODE} — the same TV endpoint in query-string form, also supported by this build. Use whichever form fits your existing code; the path form is easier to read and to share.
What is not an endpoint
There is no search endpoint, no list endpoint and no JSON metadata endpoint in the examples on this site. If a tutorial tells you to fetch JSON from a Videasy URL, it is describing a different service or an outdated pattern — the Videasy API here returns the player, not data.
Using the Videasy API in code
In most sites, the API is used by building the URL in a template, not by calling it from JavaScript. Store the TMDB ID, the title type, and, for TV, the season and episode in your database or page data, then render the iframe URL from those fields. That keeps the embed logic in one place: change the base URL once and every page on the site follows, because every page builds its URL the same way.
In React or Vue, the same idea applies: a small component that takes tmdbId, type, season and episode as props and returns an iframe with the built URL. In WordPress, a Custom HTML block with the built URL does the same job without a plugin. In plain HTML, the iframe itself is the integration.
Videasy API and TMDB: what each one does
- TMDB is the catalogue: titles, IDs, posters, overviews, seasons and episodes. You use TMDB to find the ID and, if you want it, the metadata for your page.
- Videasy is the player: given a TMDB ID, it plays that title in an iframe. It does not replace TMDB, and TMDB does not replace it.
- Your site is the glue: it stores the ID, builds the URL, and presents the page around the player. Keep those three jobs separate and each one stays simple.
See the Videasy player for the player itself, and the Videasy movies page for movie-only embeds.
Frequently Asked Questions
Is there a Videasy API with no key?
Yes, Videasy. Its embed API is URL-based: you build an iframe URL from a TMDB ID, with no API key, no token and no signup in the examples on this page.
What is the movie endpoint?
The Videasy movie endpoint is /embed/movie/ followed by the TMDB movie ID, on this host.
What is the TV endpoint?
The Videasy TV endpoint is /embed/tv/ followed by the TMDB TV ID, season number and episode number, on this host.
How do I migrate from a Videasy API integration?
Keep your TMDB IDs and replace the Videasy base URL with the Videasy embed base URL. No ID remapping is needed because both use TMDB IDs.
Is the Videasy API a JSON API?
No. The Videasy API on this site is an embed API: the URL returns the player itself in an iframe, not JSON data. For JSON metadata like titles and posters, use TMDB's own API.
Do I need a TMDB API key to use the Videasy API?
No, not for the embed itself. The Videasy embed needs only a TMDB ID in the URL. A TMDB API key is only needed if you separately fetch metadata from TMDB.
Can I use the Videasy API in a commercial site?
The embed examples on this site are shown as free, key-free iframes. This page does not give legal advice about rights for any specific title — that depends on the title and your jurisdiction, not on the embed pattern.
What happens if I use the wrong endpoint form?
A movie ID in a TV URL, or a TV ID in a movie URL, will not load the title you expect. Always match the path to the title type: /movie/ for films, /tv/ with season and episode for TV.