Webhooks
Receiving event notifications from SailPoint via webhooks/triggers.
Webhooks (event triggers) let SailPoint push notifications to your endpoint when events occur, so you react to changes instead of polling.
- Push notifications on events
- React instead of polling
- Verify signatures for security
- Respond quickly, process async
Webhooks, delivered in SailPoint via event triggers, let the platform push a notification to your endpoint the moment something happens (an identity is created, access is requested, a certification completes). This event-driven model is far more efficient than repeatedly polling the API to ask “has anything changed yet?”.
How event triggers work
You register an HTTPS endpoint to receive specific event types. When such an event occurs, SailPoint sends a signed JSON payload to your endpoint. Your service verifies the payload, acknowledges quickly, and processes the event, reacting in near-real-time instead of on a polling schedule.
Building a reliable receiver
- Verify the signature so you only act on genuine SailPoint events.
- Return 200 fast, then process asynchronously; do not do heavy work inline and risk a timeout.
- Be idempotent, the same event may be delivered more than once, so processing it twice must be safe.
- Handle retries, if you fail to acknowledge, delivery may be retried.
Webhooks versus polling
Polling wastes calls (most return “no change”) and adds latency (you only learn of changes at the next poll). Webhooks invert this: near-instant, no wasted calls. Where an event trigger exists for what you need, prefer it; fall back to polling only when no suitable event is available.
Common pitfalls
- No signature verification, accepting spoofed events.
- Heavy synchronous processing causing delivery timeouts.
- Non-idempotent handlers double-processing duplicate deliveries.