A webhook is an HTTP request, known as a callback, sent from Brazen to your system. A callback is initiated when a user performs a specific action on the Brazen platform. It then delivers information about what occurred to a specified place in your system, removing the need to monitor for updates yourself. You can configure Brazen webhooks to run when a potential attendee submits a new registration for your upcoming Brazen event and/or when a potential attendee updates their registration form.
Brazen webhooks are easy to set up and are an automated process that seamlessly sends data in real-time. By integrating webhooks, you no longer need to worry about manually checking on your event registration. You receive an update each time the specified action takes place, with the new registration information automatically delivered to your system for you to review. In the Brazen Control Center Webhooks page, you can track each time your webhook runs and whether it was successful.
| For more technical information about webhooks and how to integrate webhooks with Brazen, read our developer documentation. |
In This Article
Configure a Webhook
| You must have integrations enabled before setting up a webhook. Please contact your Brazen Account Manager about enabling integrations on your Brazen account. |
Use the Brazen Control Center to configure your webhook.
From your Account Home, select Settings. Then, click Integrations and select Webhook.
You must select Enable Webhook and then complete the necessary fields before Brazen can send any information.
Enter the Webhook URL, or endpoint, where Brazen delivers the data in JSON format to your system. This endpoint is created and provided by you and lives outside of Brazen.
Enter your Secret key that tells your endpoint that the request came from Brazen. This security features ensures you only accept callbacks from authorized sources.
Select one or more actions for which you want to receive data:
- registration.submitted — When a potential attendee submits a new registration form.
- registration.updated — When an already registered potential attendee updates their registration form, such as changing their address or uploading a new resume.
Webhook Responses
Every time a Brazen webhook runs, it receives an HTTP status code from your endpoint regarding the data delivery. This confirms whether your system successfully received the information.
The Last Webhook Result on the Webhooks page shows one of the following results for the most recent callback attempt:
- Last webhook post succeeded on [Day Date Time] — Your system successfully received the information delivered by the callback.
- Last webhook post failed on [Day Date Time] — Your system did not successfully receive the information delivered by the callback.
- No posts to current webhook — Your webhook is not enabled and has not run.
If your webhook fails, Brazen records that the delivery did not succeed but does not attempt to deliver the information again.