AsyncAPI channel · SingleFile
· SingleFile Webhooks
{subscriber_endpoint}
Channel address
{subscriber_endpoint}
Parameters
subscriber_endpoint— The HTTPS URL you configure to receive events
Operations
receive
receiveEvent
Receive a SingleFile webhook event
Messages
entity.created
Entity created
Content-Type:
application/jsonentity.updated
Entity updated
Content-Type:
application/jsondocument.created
Document available
Content-Type:
application/jsondocument.updated
Document updated
Content-Type:
application/jsondocument.deleted
Document deleted
Content-Type:
application/jsonjurisdiction.created
Jurisdiction added
Content-Type:
application/jsonjurisdiction.updated
Jurisdiction updated
Content-Type:
application/jsontask.created
Task instance created
Content-Type:
application/jsonorder.submitted
Order submitted
Content-Type:
application/jsonorder.cancelled
Order cancelled
Content-Type:
application/jsonorder.completed
Order completed
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 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.