Medusa Panel › API › Reference
The Medusa Streaming Engine API covers channels, subscribers, bouquets and cluster operations over HTTPS and returns JSON. Everything the Medusa Panel does, the API can do too. This page lists the main groups and shows the request shape.
The complete, interactive endpoint reference lives in the panel at Medusa Panel › Tools › API Documentation (it opens in a new tab). It runs Swagger UI on the engine’s OpenAPI contract, so every endpoint, its parameters and its responses are listed and can be tried out live — and it always matches your installed version.
Base URL and format
All endpoints live under /api on your panel host. Requests carry a bearer token; responses are JSON with a status field.
Endpoint groups
# channels GET /api/channel/list POST /api/channel/create # subscribers POST /api/subscriber/create GET /api/subscriber/status # bouquets and cluster GET /api/bouquet/list GET /api/cluster/status
A full example
curl -H "Authorization: Bearer YOUR_TOKEN" https://panel.example.net/api/channel/list # { "status": "ok", "channels": [ { "id": 101, "name": "Demo" } ] }
Every response has a
status field. Check it before using the rest of the body — an error returns status: error with a message instead of data.Write endpoints change live state immediately; there is no undo and no staging unless you run a separate cluster. Test write calls against a non-production panel first.
Explore with the read endpoints first. Once the JSON shapes are familiar, move to the write calls — they take the same fields you see in the read responses.
Related
- Authentication — get a token before you call anything.
- Sub-resellers and API — the same endpoints, scoped to a reseller.