GET /v1/streaming/streams

Authentication

Send an API key as a bearer token. This endpoint checks no specific permission, so any key for your organisation can call it.

This endpoint takes no organisation id. Your key already identifies the organisation it belongs to, and the response is scoped to it.

Try it

Replace anything in angle brackets with your own values, and the key placeholder with a key from your dashboard.

curl -X GET https://api.zinndigital.com/v1/streaming/streams \
  -H "Authorization: Bearer zdk_live_…"

Signed in? The API console in your dashboard fills in your real organisation id and your own key, and runs the request against the live API so you can see the actual response. Open this endpoint in the API console

Details

Live channels on the customer's own streaming account (owner ruling 2026-08-28: Gcore is sold BYO only). Connect one at /v1/connections/streaming_gcore first. ⛔⛔ The RTMP/SRT push URL is deliberately absent from this response and must never be added to it. It is a credential, not an address: anyone holding that string can broadcast as the customer. The provider's own API treats it as a secret — it offers a "reset push token" call — and the driver strips it on every list read. state is idle (channel enabled, nothing arriving), processing, ready (bytes are arriving now) or failed. ⛔ Enabled and live are different questions: rendering an enabled-but-silent channel as live sends a customer to publish a player against a manifest with nothing behind it.

Response

Errors this endpoint can return

401 · 429