SAQ DigitalDocs

    resend-webhooks

    Resend Webhooks

    The Resend Webhooks endpoints allow you to manually retry webhook deliveries for failed or missed notifications.

    Available Endpoints

    • Get Resend Status - Check status of a resend request
    • Resend Webhook - Manually trigger webhook redelivery

    Resend Process

    1. Identify failed delivery from webhook logs
    2. Submit resend request with event ID
    3. System queues redelivery attempt
    4. Webhook notification sent again
    5. New delivery log created

    Use Cases

    • Retry failed deliveries after fixing endpoint
    • Resend notifications missed during downtime
    • Reprocess events for data recovery
    • Test webhook integration

    Limitations

    • Can only resend events from last 30 days
    • Maximum 3 manual resends per event
    • Minimum 5 minutes between resend attempts
    • Original event data is preserved

    Best Practices

    • Fix endpoint issues before resending
    • Monitor logs after resend
    • Implement idempotency to handle duplicate deliveries
    • Use resend for exceptions only, not as primary flow