AsyncAPI channel · SingleFile · SingleFile Webhooks

{subscriber_endpoint}

Open source AsyncAPI → All SingleFile channels SingleFile provider profile
Provider: SingleFile AsyncAPI: v3.0.0 Spec: SingleFile Webhooks Operations: 1 Messages: 11

Channel address

{subscriber_endpoint}

Parameters

Operations

receive
receiveEvent
Receive a SingleFile webhook event

Messages

entity.created
Entity created
Content-Type: application/json
entity.updated
Entity updated
Content-Type: application/json
document.created
Document available
Content-Type: application/json
document.updated
Document updated
Content-Type: application/json
document.deleted
Document deleted
Content-Type: application/json
jurisdiction.created
Jurisdiction added
Content-Type: application/json
jurisdiction.updated
Jurisdiction updated
Content-Type: application/json
task.created
Task instance created
Content-Type: application/json
order.submitted
Order submitted
Content-Type: application/json
order.cancelled
Order cancelled
Content-Type: application/json
order.completed
Order completed
Content-Type: application/json

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.