Defining API and Webhook
API = requesting data from an Accelevents server. The request is triggered by our customers from their servers.
Webhook = automatically getting notified when data changes in Accelevents and then notifying our customer when that happens.
API
To get more out of Accelevents, you can use our API to do all sorts of useful things, like importing attendees from your existing systems or exporting attendee analytics.
Important: If you’re looking for the actual code snippets from our API, head over to our developer hub.
Note: The API feature is only available for Enterprise and White Label Plans
Webhooks
Webhooks are notifications you can subscribe to, allowing you to receive API updates when things happen in Accelevents, such as ticket purchases and attendee check-ins. You can add multiple endpoint URLs and assign specific topics to each one, allowing different event notifications to be sent to different systems or services.
You can follow the steps below to create webhooks.
Create Webhooks
Log in with either your organization or white label account. (can be accessed from the bottom left corner of any event page connected to an Organizer Profile)
Go to the Integrations tab and click Webhook to begin.
Enter your endpoint URL in the field provided, enable the Integration toggle, and click Save. You may add multiple endpoint URLs by clicking Add URL.
Note: If you don't have an end point URL, you can generate an end point URL for testing by accessing this page: https://webhook.site and copying the unique URL.
Under Webhook Topics, check the box next to each topic you want to subscribe to. If multiple endpoint URLs are configured, select the appropriate target URL from the dropdown for each topic.
That's it! Now you can test if it works!
Webhook Topics
The following webhook topics are currently available in Accelevents. Each topic represents an event that can trigger a webhook notification to your configured endpoint.
Topic | Description |
| New ticket purchased |
| User checked in |
| User checked out |
| Ticket info updated |
| Event ticket refunded |
| User registered for the session |
| User revoked registration for the session |
| User attended a session |
| Watched a session recording |
| Event created |
| Accessed the virtual event hub post event |
| User submitted a question |
| Attendee responded to poll |
| User profile updated |
| Ticket type transferred |
| Registration Request created or updated |
| Cart abandoned |
Test the Webhook
In the example above, the topic we chose is "New ticket purchased," so after setting this up, we bought a ticket to the event and checked the webhook site where we generated our end point URL. We got a notification that a ticket purchase has been made with all the attendee information.
