Skip to main content
Vyla API

​
What is Vyla API?

Vyla API is a Node.js streaming API hosted on Hugging Face Spaces. It fans out to multiple streaming providers simultaneously, verifies every stream live, and streams results back to your client in real time via Server-Sent Events (SSE) — so your player can start as soon as the first source is ready, without waiting for all providers to finish. Pass a TMDB ID. Get back a live stream of working sources, multi-language subtitles, and TMDB metadata — one event at a time.

Multi-Provider Fanout

All configured providers are queried in parallel with per-source jitter, retries, and timeouts. Dead sources are silently dropped from the stream.

Real-Time SSE Streaming

Results are pushed as Server-Sent Events the moment each provider resolves. No waiting for the slowest provider — your UI can render the first source immediately.

Built-in HLS Proxy

Stream URLs are wrapped in a server-hosted proxy that rewrites M3U8 segment and key paths. CORS issues in the browser are gone by design.

Subtitles Included

VTT and SRT subtitle tracks in multiple languages are streamed as the first event (meta) in every movie and TV response.

Download Links

A dedicated endpoint returns direct download links for movies and TV episodes with quality labels and file sizes.

Health Monitoring

A dedicated health endpoint probes every provider in real time and reports per-source latency and status.

Try the Player

Test a live stream directly in your browser — no setup needed. Enter any TMDB ID and hit play.

​
Base URL

https://missourimonster-vyla.hf.space
All endpoints return Access-Control-Allow-Origin: *. No authentication required.

​
How It Works

1

Request arrives

Your app opens an SSE connection to /movie?id= or /tv?id=&season=&episode=.
2

Meta event fires immediately

The server emits a meta event with TMDB metadata and all available subtitle tracks — before any provider has finished.
3

Parallel provider fanout

All active providers are queried simultaneously. Each source applies random jitter to stagger upstream requests, then retries on failure up to its configured limit.
4

Source events stream in

As each provider resolves and passes live verification, a source event is emitted. Your player can begin immediately on the first one.
5

Done event closes the stream

Once all providers have either resolved or timed out, a done event is sent with the total source count. The connection closes cleanly.

​
Endpoint Overview

EndpointMethodDescription
/movie?id=:idGETSSE stream of sources + meta for a movie
/tv?id=:id&season=:s&episode=:eGETSSE stream of sources + meta for a TV episode
/subtitlesGETSubtitle tracks (standalone)
/downloadsGETDownload links for movies or TV episodes
/healthGETPer-provider health check with latency
/testGETDebug a single provider in isolation
Check which providers are currently live: /health

​
SSE Event Types

All /movie and /tv responses are Server-Sent Events. Each event is a JSON-encoded line prefixed with data: .

​
meta — First event

Emitted immediately, before any provider resolves. Contains TMDB metadata and all subtitle tracks for the title. 
{
  "type": "meta",
  "meta": {
    "id": 550,
    "title": "Fight Club",
    "release_date": "1999-10-15",
    "runtime": 139,
    "vote_average": 8.438
  },
  "subtitles": [
    {
      "label": "English",
      "file": "https://sub.vdrk.site/v1/vtt/movie/550/English.vtt",
      "type": "vtt",
      "source": "v1"
    }
  ]
}

​
source — One per working provider

Emitted each time a provider passes live verification. Your player should start on the first one and fall back to subsequent ones on error. 
{
  "type": "source",
  "source": {
    "source": "provider-key",
    "label": "Provider Label",
    "url": "https://missourimonster-vyla.hf.space/api?url=...&pp=1"
  }
}

​
done — Final event

Signals the stream is complete. The total field is the number of working sources that were emitted. 
{
  "type": "done",
  "total": 14
}

​
Data Models

​
Source Object

Returned inside source events on movie and TV streams. 
{
  "source": "provider-key",
  "label": "Provider Name",
  "url": "https://missourimonster-vyla.hf.space/api?url=https%3A%2F%2F...&pp=1"
}
​
source
string
Internal provider key. Matches the keys shown in /health.
​
label
string
Human-readable provider name to display in your UI.
​
url
string
Fully-qualified, proxied, CORS-safe stream URL. For HLS sources, pass directly to hls.loadSource() — all M3U8 segment and key URIs are pre-rewritten to flow through the proxy. For MP4 sources, set as video.src directly. No base URL prepending needed in either case.

​
Subtitle Object

Returned inside the subtitles array of the meta event, and as the top-level array on the /subtitles endpoint. 
{
  "label": "English",
  "file": "https://sub.vdrk.site/v1/vtt/movie/550/English.vtt",
  "type": "vtt",
  "source": "v1"
}
​
label
string
Language name of the subtitle track, e.g. English, Spanish, Arabic.
​
file
string
Direct URL to a WebVTT (.vtt) or SRT subtitle file. Use as a <track> element src, or pass to any player’s subtitle API.
​
type
string
Format of the subtitle file — vtt or srt.
​
source
string
Internal subtitle source identifier. Informational only.

​
Download Object

Returned inside downloads[] on the /downloads endpoint. 
{
  "url": "https://...",
  "quality": "1080p",
  "size": "2.14 GB",
  "format": "MP4"
}
​
url
string
Direct download URL.
​
quality
string
Quality label, e.g. 1080p, 720p, 480p. "Unknown" if the provider doesn’t supply one.
​
size
string | null
Human-readable file size, e.g. 2.14 GB. null if unavailable.
​
format
string
Container format, e.g. MP4, MKV. Uppercase.

​
Caching

Stream results are cached in-memory with a 5-minute TTL. The per-source stream cache is keyed by source_key + tmdb_id + season + episode; the aggregate source-results cache is keyed by tmdb_id + season + episode + base. Cache hits skip the provider fetch entirely and return near-instantly. The cache resets on server restart.

​
CORS & Headers

Every endpoint returns: 
Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: GET, POST, PUT, DELETE, OPTIONS, PATCH, HEAD
Content-Type: application/json  (or text/event-stream for SSE endpoints)
Preflight OPTIONS requests return 204 No Content immediately.