Instead of polling the API every minute, subscribe your system to Illizeo events via webhooks. Profile creation, leave approval, payroll generated: your server receives a POST in under 200ms.
Available events #
| Domain | Events |
|---|---|
| employee | created, updated, archived, reactivated |
| leave | requested, approved, rejected, cancelled |
| payroll | generated, validated, exported, error |
| expense | submitted, approved, paid |
| document | uploaded, signed, downloaded |
| integration | connected, disconnected, error |
Step-by-step #
-
Create a webhook #
Settings → API → Webhooks → New. Endpoint URL, listened events, signing secret.
-
Verify the signature #
Every webhook sent is signed with HMAC SHA-256. Your server verifies to authenticate the sender.
-
Respond fast #
HTTP 200 within 5 seconds. Beyond, automatic retry with exponential backoff (1, 5, 25, 125 sec).
-
Test with ngrok or webhook.site #
For local development. The Test webhook button sends a dummy event.
-
Monitor health #
Webhook Health dashboard: success rate, latency, last failures with payload.
FAQ #
What if my server is down?
Retry for 24h with backoff. Beyond, the webhook is marked failed and you receive an alert.
How many webhooks per tenant?
Up to 50 active webhooks. Quota raisable on request.
Event order guaranteed?
No, due to retries. Use ID + timestamp to reorder if critical.
Payload format?
JSON with standard metadata (event_id, type, created_at, tenant_id) + type-specific data.
