Channel address
docv/events
Operations
subscribe
receiveDocvEvent
Receive DocV session lifecycle events
Messages
APP_OPENED
End user has opened the DocV capture flow.
Content-Type:
DOCUMENTS_UPLOADED
End user has uploaded all required documents.
Content-Type:
VERIFICATION_COMPLETED
DocV verification has completed; decision is available via Get A DocV Transaction.
Content-Type:
SESSION_EXPIRED
DocV session expired without completion.
Content-Type:
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 Agent Skill and MCP server surfaces of the same providers.
Work with this as data
Every channel here is available over the APIs.io API and to AI agents over MCP.