Webhooks and Notification service
The Eptura Engage webhook system is called the Listener service. When events occur in Eptura Engage, such as bookings being created, desks being updated, or visitors being registered, Eptura Engage sends a notification payload to a registered URL. This guide explains how to subscribe to and delete Listener webhooks using the Admin API.
Listener services provide event-driven notifications that help you build efficient, scalable integrations. Rather than repeatedly polling API endpoints for changes, you can subscribe to notifications and receive updates automatically when relevant data changes. This reduces the number of API calls required to keep external systems synchronized with Eptura Engage data.
Notification listener services
The table shows the available notification (webhooks) listener services:
Notification service |
Description |
|---|---|
| Meeting External | Provides BookingID, resource ID, and type of change. For example, a new booking, booking updates such as time/room change, or when a booking is deleted |
| MeetingProgession | Provides Booking ID, resource ID, and the type of progress (Start/Stop/Extend) and the progression method (Web/External) |
| Desk | Provides desk BookingID, resource ID, and type of change. For example, a new booking, booking updates, or when bookings are deleted |
| Deskprogression | Provides Booking ID, resource ID, and the type of progress (Start/Stop/Extend) and the progression method (Web or External) |
| Resource | Provides resource (Desk or Meeting Room) information such as resource ID, and changes to a resource such as updates, creation, and deletion |
| Visitor | Provides visitor information when created/added, updated, deleted, arrived, unarrived, departed, or undeparted |