AsyncAPI channel · Appwrite
· Appwrite Realtime API
databases.{databaseId}.collections.{collectionId}.documents
Subscribes to events for any document in a specific collection. Channel identifier pattern: `databases.[DATABASE_ID].collections.[COLLECTION_ID].documents`.
Channel address
databases.{databaseId}.collections.{collectionId}.documents
Parameters
databaseId—collectionId—
Operations
subscribe
subscribeCollectionDocuments
Receive create/update/delete events for documents in a collection.
Messages
DocumentEvent
Database document event envelope. Triggered by
`databases.*.collections.*.documents.*.create`,
`databases.*.collections.*.documents.*.update`, and
`databases.*.collections.*.documents.*.delete`.
Content-Type:
application/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.