Skip to main content

​
Overview

Vivenu uses webhooks to notify the GKL Platform of events on a seller. The development team creates four webhooks per seller: Event, Ticket, Transaction, and Checkout. They are configured under Developer > Webhooks.

​
Prerequisites

​
Naming Convention

Name each webhook using the format: 
{CONTROLLER} {REGION_CODE} {ENV}
Where {CONTROLLER} is Event, Ticket, Transaction, or Checkout, {REGION_CODE} is the uppercase hub code, and {ENV} is PROD. For example, the checkout webhook for Germany is Checkout DE PROD.

​
URL

Each webhook uses the same host and stage, changing only the controller segment and the hubRegion query parameter: 
https://en6js5j9r3.execute-api.eu-west-2.amazonaws.com/prod/api/v1/{Controller}/webhook?hubRegion={REGION_CODE}
Note the controller segment in the URL is plural (Events, Tickets, Transactions, Checkouts) while the webhook name is singular. {REGION_CODE} is the uppercase hub code, e.g. DE.

​
Creating Each Webhook

Repeat the following for all four webhooks.
1

Open the Create webhook dialog

Navigate to Developer > Webhooks and click Create.The Create webhook dialog
2

Set the name and URL

Enter the Name and URL for this webhook using the conventions above, taking the controller segment and events from the webhook reference table.
3

Set the HMAC key

Take the HMAC key generated for this hub in the New Hub Region SOP, base64 encode it, and paste the encoded value into the HMAC Key field.
Do not use the Generate HMAC Key button in Vivenu. The key must match the value stored in the GKL API configuration so the receiving API can validate incoming webhooks.
4

Select the events

Under Events, select the events for this webhook as listed in the webhook reference below.
5

Activate and save

Enable the Active toggle at the top of the dialog, then click Save Changes.

​
Webhook Reference

Webhook nameURL controller segmentEvents
Event {REGION} PRODEventsevent.created, event.updated, event.deleted
Ticket {REGION} PRODTicketsticket.created, ticket.updated
Transaction {REGION} PRODTransactionstransaction.complete, transaction.reservedBySystem, transaction.canceled, transaction.partiallyCanceled
Checkout {REGION} PRODCheckoutscheckout.completed, checkout.aborted, checkout.detailsSubmitted
The selected events for each webhook should match the screenshots below.
1

Event webhook

The selected events for the Event webhook
2

Ticket webhook

The selected events for the Ticket webhook
3

Transaction webhook

The selected events for the Transaction webhook
4

Checkout webhook

The selected events for the Checkout webhook

​
Confirming the Webhooks

Once all four are saved, the Webhooks list should show each one as active. The Webhooks list showing all four webhooks active
Last modified on June 29, 2026