AsyncAPI channel · Apache CouchDB · Apache CouchDB _changes Feed

{db}/_changes#feed=continuous

Continuous mode. The HTTP response stays open. Each change is emitted as a single line of JSON (newline-delimited JSON, NDJSON). Heartbeats are sent as empty lines on the `heartbeat` interval. After the configured `timeout`, the server emits a `last_seq` line and closes.

Open source AsyncAPI → All Apache CouchDB channels Apache CouchDB provider profile
Provider: Apache CouchDB AsyncAPI: v2.6.0 Spec: Apache CouchDB _changes Feed Operations: 1 Messages: 3

Channel address

{db}/_changes#feed=continuous

Parameters

Operations

receiveChangesContinuous
Stream NDJSON change rows on a long-lived HTTP response.

Messages

ChangeRowLine
A single NDJSON line emitted by `feed=continuous`.
Content-Type: application/json
LastSeqLine
Final NDJSON line emitted when the continuous feed closes.
Content-Type: application/json
HeartbeatLine
Empty line (continuous) or SSE comment line (eventsource) keeping the connection alive.
Content-Type: text/plain

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.