# Replay and resend

Use the Events API to catch up from your last durable cursor after an outage. Apply the same validation and event-ID deduplication as your webhook consumer, and advance the cursor only with committed effects.

`POST /v1/webhook_deliveries/{delivery}/resend` requests another delivery of the stored event. The event ID stays the business deduplication key; a resend must not create a second local user or reapply an access grant.

`POST /v1/webhook_endpoints/{endpoint}/test` sends a sample event of the requested type once. It verifies your delivery path but does not prove that a real directory or sign-in action occurred.

Fresh webhook deliveries need a fresh valid timestamp. Verify the raw body and signature on every HTTP receipt. If you deliberately process an authenticated stored delivery offline, separate that trusted storage path from the public HTTP endpoint; never disable freshness for incoming traffic.

Recover missing directory changes with [sequence-aware processing](/directory-sync/ordering/) and reconcile current state when your checkpoint no longer covers the available event history. Do not promise indefinite event retention from this interface.
