# Events and webhooks

OhAuthCat records changes as events. Your application can receive signed webhook deliveries or read the cursor-based Events API. Delivery is asynchronous; write consumers that tolerate duplicates, retries and changes arriving out of order.

Start with [raw-body signature verification](/events/webhook-verification/). Persist a verified event durably before acknowledging it, or complete the business effects before acknowledging. Respond successfully only when your application can recover the accepted work.

Endpoints configured for [WorkOS-format directory events](/directory-sync/workos-compat/#select-workos-format-webhooks) use `WorkOS-Signature` with millisecond timestamps, rather than the native verification format.

Use [Events API catch-up](/events/events-api/) after outages and [directory sequence handling](/directory-sync/ordering/) for provisioning. A webhook delivery ID identifies an attempt; the event ID identifies the business change to deduplicate.

Read [retry behavior](/events/retries/) before setting timeouts, and [replay and resend](/events/replay/) before operating a recovery path.

For local development, use the [sandbox event relay API](/events/dev-relay/) to receive live and sample events. The relay has no replay or delivery retry guarantee.

## Failover events

`edge.failover.activated` and `edge.failover.resolved` carry environment-level incident transitions rather than an organization event. See [standby incident signals](/trust/standby/#incident-signals) for their data and operational boundaries.

The [event catalogue](/reference/webhook-events/) lists public event types. [Log streaming](/events/log-streaming/) is a separate add-on available on every plan; it exports bounded audit and sign-in projections, not raw authentication traffic, and does not promise exactly-once external delivery.
