Overview:

This release introduces Automatic Webhook Retry, a new system-level feature designed to improve webhook delivery reliability. When a webhook delivery attempt fails, the platform will now automatically retry sending the webhook up to four times using an incremental backoff schedule. In addition, a new Webhook Retry API endpoint allows clients to manually trigger a retry under specific conditions.

1. Automatic Webhook Retry — failed webhook deliveries now retry automatically with a structured backoff schedule.
2. Webhook Retry API — allows clients to manually trigger a one-time retry for failed webhooks.
3. List Webhooks API — enables clients to inspect webhook history, including attempts, statuses, payloads, and headers

This release includes:

• Automatic retry behaviour
• Manually trigger a webhook retry
• Webhook listing endpoint
• Request & response objects
• Field definitions

These additions significantly improve webhook monitoring, troubleshooting, and resilience.

Automatic Webhook Retry Logic:

When a webhook delivery attempt fails, it is automatically placed into a retry cycle with incremental delay intervals:

Rules:

Retries stop immediately upon a successful attempt. After five total failed attempts, the webhook is permanently marked as failed. No client action is required for this mechanism — it operates internally and transparently.

List Webhooks API

A new paginated endpoint allows clients to retrieve webhook history, including delivery attempts, retry counts, timestamps, and payloads. List Webhook API

Features

• View webhook events with full information
• Retrieve request/response logs
• Understand retry behaviour, including numberOfAttempts and lastAttemptDateTime
• Fetch webhookId values for debugging or manual retry
• Paginate through historical webhook activity

Webhook Retry API (Manual Retry)

A dedicated API endpoint now allows clients to manually retry a webhook exactly once, using the webhook’s unique identifier. Retry Webhook API

Behaviour & Validation

• Manual retries are only permitted for webhooks in the failed state.
• The API will reject the request and return an error if the webhook status is "processing" or "successful".
• A manual retry does not restart or extend the automatic retry schedule.
• The manual retry is executed as a single, immediate attempt.