AsyncAPI channel · fauna · Fauna Event Streaming

/stream/1

Event stream channel for real-time change data capture. Clients send a POST request with an event source token to open a persistent connection. Fauna pushes events through the open connection as changes occur in the subscribed document or set. The connection remains open until closed by the client or server. If a tracked change occurs, the event source emits a related add, remove, or update event.

Open source AsyncAPI → All fauna channels fauna provider profile
Provider: fauna AsyncAPI: v2.6.0 Spec: Fauna Event Streaming Operations: 2 Messages: 5

Channel address

/stream/1

Operations

publish
receiveStreamEvents
Receive real-time change events
subscribeToStream
Subscribe to an event stream

Messages

StatusEvent
Heartbeat or connection status event sent when the stream is opened or periodically to keep the connection alive.
Content-Type: application/json
AddEvent
Event emitted when a new document is added to the tracked set or a document begins matching the tracked criteria.
Content-Type: application/json
RemoveEvent
Event emitted when a document is removed from the tracked set or a document stops matching the tracked criteria.
Content-Type: application/json
UpdateEvent
Event emitted when a tracked document is updated.
Content-Type: application/json
StreamSubscription
Request to open an event stream connection.
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.