Webhook Deliveries

Retry a webhook delivery

Queue an immediate retry of this delivery. The delivery is marked pending, its attempt count is reset to 0 and next_retry_at is set to now, and it is queued for delivery at once. Calling retry on an already-pending delivery queues it again. Failed and dead-lettered deliveries can be retried; a delivery that already succeeded cannot (409 already_succeeded).

POST/webhook-deliveries/{id}/retry

Queue an immediate retry of this delivery. The delivery is marked pending, its attempt count is reset to 0 and next_retry_at is set to now, and it is queued for delivery at once. Calling retry on an already-pending delivery queues it again. Failed and dead-lettered deliveries can be retried; a delivery that already succeeded cannot (409 already_succeeded).


Related endpoints

  • GET /webhook-deliveries — List webhook deliveries
  • GET /webhook-deliveries/{id} — Retrieve a webhook delivery

Common errors

  • 404 resource_missing — the referenced resource does not exist or is not visible to your key.
  • 409 conflict — Idempotency-Key collision with a different body, or a concurrent state-transition conflict.

Idempotency

Pass an Idempotency-Key header (UUID v4 recommended) to make retries safe. Keys are valid for 24 hours; see the idempotency guide.

x-api-key<token>

Your RevKeen merchant API key. Create and manage keys in Dashboard → Settings → Developer. Use rk_sandbox_* for staging/test and rk_live_* for production. The same key may be sent as Authorization: Bearer <key> if that suits your HTTP client better. A missing, invalid, expired, or revoked key returns 401 with a WWW-Authenticate: Bearer challenge; a valid key without the required scope returns 403.

In: header

Path Parameters

id*string

Webhook delivery ID

Formatuuid

Response Body

application/json

application/json

application/json

application/json

application/json

Stuck on an error response? Ask the RevKeen assistant to explain it.
curl -X POST "https://api.revkeen.com/v2/webhook-deliveries/11111111-1111-4111-8111-111111111111/retry" \
  -H "x-api-key: $REVKEEN_API_KEY"

Synthetic documentation data, validated against the response schema; not a live API result.

{  "data": {    "id": "550e8400-e29b-41d4-a716-446655440000",    "object": "webhook_delivery",    "endpoint_id": "7c1cbf21-0b6c-4c27-9d60-8a9f0a7e6d91",    "event_id": "1f8d9e0b-3a2e-4d9a-b0fe-1c2a3f4d5e6f",    "event_type": "invoice.paid",    "status": "pending",    "attempts": 2,    "max_attempts": 8,    "last_status_code": 502,    "last_error": "connect ETIMEDOUT",    "last_error_code": "ETIMEDOUT",    "last_duration_ms": 1532,    "last_attempt_at": "2019-08-24T14:15:22Z",    "next_retry_at": "2019-08-24T14:15:22Z",    "delivered_at": "2019-08-24T14:15:22Z",    "dead_lettered_at": "2019-08-24T14:15:22Z",    "dead_letter_reason": "string",    "created_at": "2026-09-01T12:00:00Z",    "updated_at": "2026-09-01T12:00:00Z"  }}

Put this endpoint to work