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:
Channel address
Parameters
feed_id— The Knock in-app feed channel UUID.user_id— The Knock user identifier of the subscribed recipient.
Operations
Messages
application/jsonapplication/jsonapplication/jsonapplication/jsonapplication/jsonapplication/jsonapplication/jsonAbout 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.