We’re excited to announce the 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 paid
Booking participant created
Booking participant updated
Booking participant cancelled
We don't have feature parity with webhooks v1 just yet. If there's any endpoints missing, please let us know here.
🔧 How can I configure Webhooks v2?
In your Appointedd account at app.appointedd.com, you'll only be able to configure webhooks v1. To configure webhooks v2, you will need have access to the new Enterprise Management Console at console.appointedd.com. You must be Administrator to access the Console.
Once you setup the webhooks in the Console, it will apply to your accounts as usual, as long as you select them. You just won't visually see them setup in the back office at app.appointedd.com, only console.appointedd.com.
Please note you can use webhooks v1 and webhooks v2 simultaneously.
Follow the below procedure to configure webhooks v2 in the Console:
Steps | Instruction |
1) Fill in the Label | This is the internal name for your configuration |
2) Enter the Destination URL | This is the URL that the payload will be sent to when an event is triggered |
3) Tick which Event Triggers you want to configure | These are the type of events that will be sent to the destination URL |
4) Fill in your Account Selection | Tick the accounts your webhook configuration applies to |
5) Add Custom HTTP Header (optional) | Optionally provide a custom header that will be included in the webhook HTTP request. After a configuration is saved, existing header values cannot be viewed or edited for security reasons. You can disable custom headers or replace the entire configuration if you need to change them |
6) Enter Header Key and Header Value (if using custom HTTP Header) | e.g. Authorization and Bearer token123 |
7) Hit Save! | Once saved, you'll see it listed in your Webhook Configurations, and it will be live. |
🔧 Testing the Webhooks V2
TBC.