AccessOwl can send real-time Webhooks to a URL of your choice whenever key events occur. Use webhooks to trigger workflows in your own systems—such as provisioning internal resources, updating a ticketing system, or kicking off custom automation.
Setup
- Go to Settings → Webhooks in the AccessOwl admin interface.
- Click “Add Webhook”.
- Enter the endpoint URL where AccessOwl should send event payloads.
- Select the events you want to subscribe to.
- Save. AccessOwl will start delivering events immediately.
Your endpoint must respond with an HTTP 2xx status code within 10 seconds, otherwise the delivery is considered failed and AccessOwl will retry.
Payload structure
Every webhook payload is a JSON object with the following top-level fields:
| Field | Type | Description |
|---|
event_type | string | The event that triggered this webhook (e.g. onboarding.created) |
org_id | string | The UUID of your AccessOwl organization |
data | object | Event-specific data (see event documentation) |
Retries
If your endpoint returns an HTTP 4xx or 5xx response, or the connection fails, AccessOwl retries the delivery up to 9 times (a maximum of 10 delivery attempts in total) using exponential backoff. The delay starts at ~2 minutes and roughly doubles with each retry, capped at 3 hours:
| Retry | Approximate delay |
|---|
| 1st | ~2 minutes |
| 2nd | ~4 minutes |
| 3rd | ~8 minutes |
| 4th | ~16 minutes |
| 5th | ~32 minutes |
| 6th | ~1 hour |
| 7th | ~2 hours |
| 8th–9th | ~3 hours each |
