Skip to main content
POST
Retry a failed webhook notification
Manually retries a FAILED webhook notification, queuing it for immediate re-delivery to your configured webhook URL. The automatic retry cycle is reset and manualRetryCount is incremented.

Important Notes

  • Status requirement: The notification must be in FAILED status. Attempting to retry a SENT, PENDING, or NOT_SENT notification returns a 409.
  • Manual retry limit: Each notification allows a maximum of 3 manual retries. Once reached, the endpoint returns 409 and the notification cannot be retried again.
  • Rate limit: A maximum of 10 manual retries per partner per minute is enforced. Exceeding this returns 429.
  • Automatic retry reset: On a successful retry request, retryAttempts is reset to 0 and latestErrorPayload is cleared, giving the notification a fresh delivery cycle.

When to Retry vs. When to Contact Support

Retry when:
  • Your endpoint was temporarily unavailable (e.g. a deployment, a transient 5xx).
  • You fixed a bug in your webhook handler and need the event reprocessed.
  • The latestErrorPayload shows a recoverable error (connection timeout, 503, etc.).
Contact support when:
  • Your webhook URL has changed — update it first via PUT /api/partner/v2/webhook-settings, then retry.
  • The event payload is stale and the corresponding transaction has already been handled through another channel.
  • You have exhausted all 3 manual retries and still cannot receive the notification.

Error Codes

Common Errors

Endpoint-Specific Errors

Authorizations

partner-api-key
string
header
required

API key for the affiliated partner performing the request.

Path Parameters

id
string
required

The webhook notification ID to retry

Example:

"8374f327-38bd-4b0b-b8a7-2524599eb903"

Response

Notification successfully queued for re-delivery. Returns the updated notification with status reset to PENDING.

success
boolean
Example:

true

data
object