Defining API and Webhook
APIs and webhooks are options for Accelevents and other systems to share information with each other. They help automate processes and keep data synced between platforms.
Here’s a simple example for each using event registrations in Accelevents:
API Example
Your company wants to display the latest event registrations in your website dashboard. Your system can use the Accelevents API to request attendee and registration data whenever the dashboard is opened or refreshed.
Webhook Example
Your company wants to automatically notify your sales team every time someone registers for an event. Instead of constantly checking for new registrations, you can set up a webhook in Accelevents. Whenever a new registration happens, Accelevents automatically sends the attendee information to your system in real time.
This is mainly the difference:
API - a way for your system to request data from Accelevents on demand.
Webhook - a way for Accelevents to automatically notify your system in real time when an event or data change occurs.
API
This feature is available only for Enterprise and White Label Plans
An API (Application Programming Interface) is a set of rules that allows different systems or applications to communicate with each other.
APIs let one application request or send data to another application in a structured and secure way. Instead of accessing a system’s database directly, developers can use API endpoints to retrieve, create, update, or delete information.
For example, using the Accelevents API may allow you to:
Retrieve attendee information
Create or update registrations
Access event or session details
Generate reports
Sync data with external platforms such as CRMs or marketing tools
APIs typically work through HTTP requests such as:
GET – Retrieve data
POST – Create new data
PUT/PATCH – Update existing data
DELETE – Remove data
Most modern APIs return data in JSON format, making it easy for systems to process and integrate information automatically.
APIs are commonly used for:
System integrations
Custom applications
Automated workflows
Reporting and analytics
Connecting third-party platforms and services
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.
If you’re looking for the actual code snippets from our API, head over to our developer hub.
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.
How Does it Work?
A webhook is a way for one system to automatically send real-time data to another system when a specific event / action happens.
Instead of repeatedly checking for updates, the receiving system provides a webhook endpoint URL where it wants to receive notifications. When the selected event occurs, the sending system automatically sends an HTTP request—usually a POST request—to that endpoint with relevant data in the payload.
For example, if you configure a webhook for the topic “New Ticket Purchased,” the platform will automatically send attendee and ticket purchase information to your endpoint every time someone buys a ticket.
Note: If you don't have an end point URL, you can generate one for testing through various free sites such as the following:
Setup Webhooks
Go to your Organizer Portal or Enterprise / White Label Dashboard
Go to Integrations > Webhooks
Enter your endpoint URL in the field provided. You can add multiple endpoint URLs by clicking Add URL
Enable the Integration toggle, and click Save.
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!
Test the Webhook
To test if your webhook works for new registrations (ticket_purchase_event topic), register for any event under your account. The webhook endpoint will then receive a notification payload containing the ticket purchase details, including the attendee information.
With your webhook connected in the organizer / enterprise / white label level, you will receive a notification payload for any registration for any event in your account, regardless of how they registered as long as the order is already created.
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 |
Other Examples of Webhook Uses




