Health Check

Probe all configured providers in real time and get per-source latency and status.

GET /api/health

Health Check

cURL

curl --request GET \
  --url https://missourimonster-vyla.hf.space/api/health

200

{
  "status": "<string>",
  "timestamp": "<string>",
  "tmdb": true,
  "cache": 123,
  "probe_id": "<string>",
  "sources": {
    "ok": true,
    "ms": {}
  }
}

The health endpoint probes every active provider using a known-good TMDB ID and reports whether each one is up, along with the response time in milliseconds. No parameters needed.

Health checks are not cached. Each call triggers a fresh live probe of all active providers — expect a response time of 2–10 seconds depending on provider count and speed.

---

Request

cURL

curl https://missourimonster-vyla.hf.space/api/health

---

Response Fields

status · string · required

Overall health of the API.

• "ok" — all providers returned a valid stream
• "degraded" — one or more providers failed; others still work

timestamp · string · required

ISO 8601 timestamp of when the health check was run.

tmdb · boolean · required

Whether a TMDB_API_KEY is configured. false means the meta field will be null in movie and TV responses.

cache · number · required

Number of entries currently in the in-memory stream cache.

probe_id · string · required

The TMDB ID used to probe all providers during this health check.

sources · object · required

Per-provider health results, keyed by provider key.

Show Per-source object

ok · boolean

true if the provider returned a valid, playable HLS stream during this probe.

ms · number | null

Response time in milliseconds. null if the probe threw an error before a response was received.

---

Responses

200 — All OK

All providers are live and returned valid streams.

{
  "status": "ok",
  "timestamp": "2025-06-01T12:00:00.000Z",
  "tmdb": true,
  "cache": 12,
  "probe_id": "155",
  "sources": {
    "provider-a": { "ok": true, "ms": 1204 },
    "provider-b": { "ok": true, "ms": 980  },
    "provider-c": { "ok": true, "ms": 2100 }
  }
}

207 — Degraded

One or more providers failed. HTTP status is 207 Multi-Status. Working sources are still usable.

{
  "status": "degraded",
  "timestamp": "2025-06-01T12:00:00.000Z",
  "tmdb": true,
  "cache": 4,
  "probe_id": "155",
  "sources": {
    "provider-a": { "ok": true,  "ms": 1204 },
    "provider-b": { "ok": false, "ms": 435  },
    "provider-c": { "ok": false, "ms": 1138 }
  }
}

---

Status Reference

HTTP	status field	Meaning
200	"ok"	All providers healthy
207	"degraded"	At least one provider down

A 207 Degraded response does not mean the API is unusable. Movie and TV endpoints will still return sources from whichever providers are working. Check data.sources.length > 0 rather than depending on status === "ok" when deciding whether to proceed.