AsyncAPI channel · Novu
· Novu Notification Center WebSocket API
/
The single Socket.IO default namespace (`/`). All Novu Notification Center events are emitted on this namespace, addressed to the room identified by the authenticated subscriber's internal `_id`. Clients do not need to `join` or `subscribe` — the server joins the socket to the correct room during the handshake (see `bindings.ws` below for the handshake auth contract).
Provider:NovuAsyncAPI: v2.6.0Spec: Novu Notification Center WebSocket APIOperations: 1Messages: 3
Channel address
/
Operations
subscribe
subscribeNotificationCenter
Receive real-time Notification Center events for the authenticated subscriber.
Messages
notification_received
A new in-app notification was delivered to the authenticated subscriber's inbox.
Content-Type: application/json
unread_count_changed
The subscriber's unread in-app notification count changed.
Content-Type: application/json
unseen_count_changed
The subscriber's unseen in-app notification count changed.
Content-Type: application/json
About AsyncAPI
The AsyncAPI specification describes event-driven APIs the way OpenAPI describes request/response APIs. A channel is the named pipe — a webhook URL, a Kafka topic, a WebSocket route, an MQTT subject — that producers and consumers publish or subscribe to. Each channel carries one or more messages with structured payloads, and an operation declares whether a given party sends or receives on that channel.
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.