Skip to content
Dashboard
Theme
Theme

Events and webhooks

Every change is recorded as an event. You can receive events as signed, retried webhooks or read them with the cursor-based Events API.

View Markdown

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. 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 use WorkOS-Signature with millisecond timestamps, rather than the native verification format.

Use Events API catch-up after outages and directory sequence handling for provisioning. A webhook delivery ID identifies an attempt; the event ID identifies the business change to deduplicate.

Read retry behavior before setting timeouts, and replay and resend before operating a recovery path.

For local development, use the sandbox event relay API to receive live and sample events. The relay has no replay or delivery retry guarantee.

edge.failover.activated and edge.failover.resolved carry environment-level incident transitions rather than an organization event. See standby incident signals for their data and operational boundaries.

The event catalogue lists public event types. 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.