AsyncAPI channel · Tripleseat · Tripleseat Webhooks

`/`

The subscriber URL that receives webhook POST requests.

Open source AsyncAPI → All Tripleseat channels Tripleseat provider profile

Provider: Tripleseat AsyncAPI: v3.0.0 Spec: Tripleseat Webhooks Operations: 1 Messages: 5

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/json

CREATE_INTERNAL_LEAD

A lead was created internally within Tripleseat.

Content-Type: application/json

CONVERT_LEAD

A lead was converted into an account and contact.

Content-Type: application/json

CONVERT_LEAD_TO_BOOKING

A lead was converted into an event or booking.

Content-Type: application/json

LEAD_TURNED_DOWN

A lead was turned down.

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 Naftiko capability, Agent Skill, and MCP server surfaces of the same providers.