We’re excited to announce the upcoming release of our webhooks v2!
With enriched event data and detailed audit trails, you can monitor webhook delivery status and debug issues effectively.
The introduction of enhanced retry mechanisms ensures that critical events are reliably delivered, significantly improving the robustness of integrations with external systems.
This reduces operational disruptions for businesses like yours, that rely on webhooks to trigger business-critical workflows.
👀 What’s improved in webhooks v2?
Webhook processing
Webhook events will be received, validated, and processed in a structured manner. Each event will be enriched with relevant metadata before being delivered to your configured endpoint. In the event of any processing issues, the system will ensure reliable delivery through automatic retries.
Webhook logging and monitoring
Webhook payloads, responses, and failure logs are securely stored, allowing you to track activity with detailed logging and diagnostics, helping you quickly troubleshoot any delivery issues.
Webhook configuration
You will have flexibility in defining webhook configurations:
A global webhook endpoint can be configured to receive all event types.
Specific event types can have designated webhook endpoints for granular routing.
An API will be provided to update webhook configurations dynamically.
The Enterprise Management Console will allow you to centrally manage all webhook configurations.
Webhook future-proof architecture
Webhook v2 enables faster delivery and will support additional event types:
Invoice created
Invoice updated
Booking rescheduled
Participant booked
Participant rescheduled
Participant cancelled
🔧 When/how can I start using webhook v2?
Please continue using webhooks v1 for now - there’s no immediate action required.
We’ll notify you as soon as webhooks v2 is live, so you can plan your transition and start taking advantage of the new enhancements.
We will also provide a deprecation timeline for webhooks v1 well in advance and will support you throughout the migration. At this time, there are no set plans for deprecation.
