Tripleseat · AsyncAPI Specification
Tripleseat Webhooks
Version v1
Tripleseat webhooks POST a JSON package to a subscriber URL when a lead or booking lifecycle event occurs. Each request carries an X-Signature header computed with SHA256-HMAC using the webhook endpoint's signing key, which subscribers should verify with a constant-time comparison. Subscribers must return HTTP 200 on receipt; otherwise Tripleseat re-sends the same POST up to five additional times. Webhooks are configured under Settings → Tripleseat API.
Channels
webhook
The subscriber URL that receives webhook POST requests.
Messages
LeadCreated
Lead Created
A new lead was created (for example, via the public lead form).
InternalLeadCreated
Internal Lead Created
A lead was created internally within Tripleseat.
LeadConverted
Lead Converted
A lead was converted into an account and contact.
LeadConvertedToBooking
Lead Converted To Booking
A lead was converted into an event or booking.
LeadTurnedDown
Lead Turned Down
A lead was turned down.
Servers
https
subscriber
The subscriber endpoint URL you register in Tripleseat. Tripleseat POSTs webhook payloads to this URL.