Set up Webhooks
Use Webhooks when you want Quicket to automatically send information to another system when specific ticket-buying activity takes place.
A webhook sends data to a listening URL when the selected action occurs.
What can trigger a webhook?
Quicket currently provides event webhooks for:
- A user starting checkout
- Checkout being cancelled
- A user booking tickets to pay by EFT
- Checkout being completed after payment is received
You can use one or more of these hooks.
What can Webhooks be used for?
For example, you could:
- Add attendees to a CRM
- Update an internal database
- Add booking information to a spreadsheet
- Send personalised messages
- Follow up on abandoned checkouts
Before you begin
You'll need a listening URL.
This is an internet address where your system is ready to receive the information Quicket sends.
Your CRM may provide one, or a developer can create one for you.
Set up a Webhook
1
Open your Event Dashboard.
2
Go to Settings → Integrations → Webhooks.
3
Find the hook you want to enable.
4
Enter the listening URL.
5
Make sure the receiving system is ready.
You can use the same listening URL for several hooks or different URLs for each one.
What information does Quicket send?
Webhook information is sent in JSON format, a standard format commonly used when exchanging data between applications.
Your receiving system or developer will need to interpret this information and decide what should happen when it arrives.
Don't have a developer?
If you don't have a system capable of receiving Webhooks, consider using Zapier instead.
What’s next?
Choose the integration approach that best fits your technical setup and automation requirements.