Overview

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

1. Go to Settings → Webhooks in the AccessOwl admin interface.
2. Click “Add Webhook”.
3. Enter the endpoint URL where AccessOwl should send event payloads.
4. Select the events you want to subscribe to.
5. 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 19 times using exponential backoff. The delay starts at ~40 seconds and doubles with each attempt, capped at 2 hours:

Retry	Approximate delay
1st	40 seconds
2nd	80 seconds
3rd	~3 minutes
4th	~5 minutes
5th	~11 minutes
6th	~21 minutes
7th	~43 minutes
8th	~85 minutes
9th–19th	~2 hours each

A small random jitter (~10%) is added to each retry. Delivery attempts that are still pending after 24 hours from the original event are cancelled and will not be retried further.

You can inspect all delivery attempts from Settings → Webhooks.