Build around available event operations
Retrieve activity through the event API and process records in your application.
Webhook availability
The API covered by this reference does not define a general webhook-registration operation. Use the event retrieval routes for the integration workflow below.
POST
/v1/event/list
Retrieve recent activity
Authenticate with a session whose role includes can_view_events. Start from the newest records, then use next_cursor to retrieve older batches.
Request Example
curl -X POST "https://your-lexoh-server.app.lexoh.com:3000/v1/event/list" \
-H "SessionID: SESSION_TOKEN" \
-H "Content-Type: application/json" \
-d '{"cursor_id":0,"page_limit":25}'Keep synchronization predictable
- Track processed event ids so repeated reads do not duplicate downstream actions.
- Keep filters consistent while paging through a batch.
- Check success and error along with the HTTP status before updating local state.
- Set request frequency and concurrency for the integration’s workload; do not assume a webhook delivery guarantee.