Configuring event webhooks

Event webhooks

Please contact support to ensure that this feature is enabled for your plan.

Event webhooks allow you to configure events to send notifications to your server when certain events occur in the event lifecycle. These events currently include attendee registration and invitation events.

You will need to create a webhook endpoint on your server to receive the event notifications. This endpoint should be a publicly accessible URL that can receive POST requests.
Make a note of the URL for your webhook endpoint.

Log in to your getregistered account and navigate to the integrations dashboard.
Click on the Webhooks tile then click to add a new integration.
Enter the URL for your webhook endpoint.
Select which events you'd like the webhook to receive notifications for.
Click Save to save your changes.

getregistered only supports https - not http - for webhook endpoints.
HTTP Basic Authentication is supported. If you add the generated basic auth token to the webhook settings, it will be added to the Authorization: Basic header of the webhook request.
getregistered adds a HMAC signature to each event notification sent to your webhook endpoint. This signature is calculated using a secret key that we generate for you and can supply securely via support. You should verify this signature to ensure that the event notification was sent by getregistered and has not been tampered with. The signature is included in the X-Getregistered-Signature header of the webhook request. It is the HMAC SHA256 digest of the request body using the secret key as the key.

If your webhook endpoint returns a non-2xx response, getregistered will retry sending the notification up to 10 times with an exponential backoff delay between retries.
getregistered will always send the latest version of registration data in the event payload, not the data at the time of the event.