{db}/_changes#feed=eventsource
EventSource mode. Same semantics as `continuous` but framed as Server-Sent Events (`text/event-stream`). Each change is delivered as an `event: ` / `data: ` block, with `id:` set to the row's `seq`. Heartbeats are emitted as SSE comment lines. The endpoint honors the `Last-Event-ID` header for reconnects.
Channel address
Parameters
db—
Operations
Messages
text/event-streamAbout 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.