---
title: "Subscribe to real time events."
method: GET
path: "/api/v1/events/subscribe"
tags: ["Events"]
---

# Subscribe to real time events.

`GET /api/v1/events/subscribe`

Subscribe to events. An `EventSource` can be used to listen to events (the
Swagger test page won't work).

Each client connection is unique to that client app, and clients will only
receive the events that are meant for them.

Authenticate with the standard `Authorization` header. Clients built on the
native browser `EventSource` cannot send headers; those can send the JWT in
the deprecated `authorization` query param instead.<br /><hr /><h3>🛡️ Requires Capabilities: None</h3>

## Query parameters

- `authorization` unknown

## Response `200`

## Other responses

- `401` — Possible reasons: The authorization token is invalid.

## Changes

- **2026-07-22** `fafce3d5aa9e` — 5 info
  - the endpoint scheme security `Local User JWT` was added to the API
  - the `query` request parameter `authorization` became optional
  - `query` request parameter `authorization` was deprecated
  - for the `query` request parameter `authorization`, the type/format was generalized from `string`/`` to ``/``
  - …1 more

[Change history](https://skmtc.dev/cardinalapps/apis/cardinal-media-server-api/changes/api/v1/events/subscribe/get.md)

---

[API](https://skmtc.dev/cardinalapps/apis/cardinal-media-server-api.md) · [All operations](https://skmtc.dev/cardinalapps/apis/cardinal-media-server-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/cardinalapps/cardinal-media-server-api/revisions/7b5e4555e84f/schema)