Signed webhooks for every booking and payment event
Stream every booking and payment event into your own systems — CRM, data warehouse, Slack, custom integrations. HMAC-signed, retried with exponential backoff, and fully logged. Built for engineering teams who refuse to poll an API.
Why engineering teams pick Triviyo webhooks
Standard patterns, predictable behavior, and a delivery log that actually helps you debug.
HMAC signatures on every payload
Every webhook is signed with HMAC-SHA256 using your endpoint's secret. Verify the signature before acting on the payload — same pattern as Stripe, GitHub, and every other webhook you already trust.
Retries with exponential backoff
If your endpoint times out or returns 408, 429 or a 5xx status, Triviyo retries the delivery automatically, up to 6 attempts in total. Any other 4xx response is treated as permanent and is not retried.
Standard event names
BOOKING_CREATED, BOOKING_UPDATED, BOOKING_CANCELED, PAYMENT_SUCCEEDED, PAYMENT_FAILED, REFUND_PROCESSED. Subscribe to exactly the events your integration needs; ignore the rest.
Per-endpoint signing secrets
Each endpoint gets its own signing secret, which you can regenerate at any time under Settings → Webhooks.
Full delivery log
Every delivery attempt is logged in the dashboard with its HTTP status, response and timestamp.
Triviyo webhooks vs. polling a REST API
What real-time event streaming looks like compared to hammering a REST endpoint.
| What the webhooks API ships with | Triviyo | Without Triviyo |
|---|---|---|
| Availability | Professional tier and up | Enterprise API access only |
| BOOKING_CREATED | ||
| BOOKING_UPDATED | ||
| BOOKING_CANCELED | ||
| PAYMENT_SUCCEEDED | ||
| HMAC-SHA256 signatures | Enterprise add-on | |
| Retry strategy | Up to 6 attempts | One attempt or none |
| Delivery log | ||
| Support | Priority support | Email ticket queue |
Standard patterns — nothing exotic, nothing proprietary.
Frequently asked questions
What events can I subscribe to?
BOOKING_CREATED, BOOKING_UPDATED, BOOKING_CANCELED, PAYMENT_SUCCEEDED, PAYMENT_FAILED, REFUND_PROCESSED. Subscribe per-endpoint to exactly what your integration needs.
How do I verify the webhook is really from Triviyo?
Every payload is signed with HMAC-SHA256 using your endpoint's unique secret. Verify the X-Webhook-Signature header against the raw request body before acting — same pattern as Stripe and GitHub webhooks. Code examples are in our docs.
What happens if my endpoint is down?
Triviyo makes up to 6 delivery attempts in total. After the last one, the delivery is marked as failed in the delivery log. A 4xx response other than 408 or 429 marks the delivery as failed straight away, without retries.
Can I test webhooks in a staging environment?
Yes. Send a test delivery to any endpoint under Settings → Webhooks to check your integration before going live.
What tier do I need for webhooks?
Professional tier and up.
Build real-time integrations that don't poll
Signed, retried, logged — exactly how engineering teams expect webhooks to work.
14-day free trial. No credit card required. Cancel anytime.