AsyncAPI channel · Knock · Knock Real-Time In-App Feed (Phoenix Channels)

feeds:{feed_id}:{user_id}

Per-user, per-feed Phoenix Channel topic. `feed_id` is the Knock in-app feed channel identifier (a UUID configured in the Knock dashboard). `user_id` is the Knock user identifier of the authenticated recipient. Source: `socketChannelTopic` in the Knock JS SDK returns ``feeds:${feedId}:${userId}`` and the in-source comment in `socket-manager.ts` documents the topic as `feeds::

Provider: Knock AsyncAPI: v2.6.0 Spec: Knock Real-Time In-App Feed (Phoenix Channels) Operations: 2 Messages: 7

Channel address

feeds:{feed_id}:{user_id}

Parameters

Operations

publish
sendChannelControl
Phoenix Channel control frames sent by the client.
receiveFeedEvents
Receive real-time updates for an in-app feed.

Messages

phx_join
Client request to join the feed channel.
Content-Type: application/json
phx_leave
Client request to leave the feed channel.
Content-Type: application/json
heartbeat
Periodic heartbeat sent by the client to keep the socket alive.
Content-Type: application/json
new-message
Emitted by Knock when a new in-app message has been produced for the subscribed user/feed. Does not contain the full message; it carries the updated feed `metadata` (badge counts) and an `attn` list n
Content-Type: application/json
phx_reply
Server reply to a client push (e.g. response to `phx_join`).
Content-Type: application/json
phx_error
Channel-level error pushed by the server.
Content-Type: application/json
phx_close
Channel closed by the server.
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.

Browse every event-driven channel on the APIs.io network or compare with the broader Naftiko capability, Agent Skill, and MCP server surfaces of the same providers.