AsyncAPI channel · Tripleseat
· Tripleseat Webhooks
/
The subscriber URL that receives webhook POST requests.
Channel address
/
Operations
receive
receiveWebhook
Receive A Tripleseat Webhook
Messages
CREATE_LEAD
A new lead was created (for example, via the public lead form).
Content-Type:
application/jsonCREATE_INTERNAL_LEAD
A lead was created internally within Tripleseat.
Content-Type:
application/jsonCONVERT_LEAD
A lead was converted into an account and contact.
Content-Type:
application/jsonCONVERT_LEAD_TO_BOOKING
A lead was converted into an event or booking.
Content-Type:
application/jsonLEAD_TURNED_DOWN
A lead was turned down.
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.