Skip to content
TicketingHub Help

How to Set Up Webhooks

Webhooks send selected TicketingHub events to another system as they happen.

Before you start

  • Webhooks must be enabled for your TicketingHub account. Contact TicketingHub if the Webhooks section is missing.
  • You need administrator or manager access.
  • The receiving system must provide a public HTTPS URL.

Add a webhook

  1. Go to Settings → Advanced.
  2. Find Webhooks and select Edit.
  3. Select New Webhook.
  4. Enter the HTTPS URL that will receive the events.
  5. Select the event types to send, such as a confirmed or cancelled booking.
  6. Optional: enter a strong secret so the receiving system can verify each request.
  7. Create the webhook, then perform one of the selected events to test it.

If you add a secret, TicketingHub signs each request and sends the signature in the X-TicketingHub-Signature-256 header. Your developer should verify this signature before accepting the data.

Keep the webhook active

The receiving system should respond with a successful 2xx status promptly. TicketingHub retries deliveries that time out or return an unsuccessful response. An endpoint that continues to fail is automatically disabled; fix the receiving system, then return to the Webhooks page and enable it again.

TicketingHub only sends events to public addresses. If the URL points to a private network address, such as a server inside your own network, TicketingHub does not send the event and disables the webhook straight away. The Webhooks page shows “The URL points to a private network address” and your account admins receive an email. Change the URL to a public HTTPS address, then enable the webhook again.

Choose only the events you need and avoid using a test URL in a live account. To send events to Zapier without building your own receiver, see How to Connect TicketingHub to Zapier. To build an integration that also requests data from TicketingHub, see How to Create and Use an API Token.