Webhooks

Retry a failed webhook delivery

Deprecated. Use POST /v1/accounts/{account_id}/webhooks/{webhook_id}/deliveries/{delivery_id}/retry, which behaves identically.

Re-sends the original payload of a delivery immediately.

  • Payload: the one captured when the event happened, not a fresh snapshot, so changes made to the entity since then are not reflected.
  • History: the outcome is recorded as a new entry and the original entry is kept as it was. attempt_number continues the same sequence, so it can exceed the number of automatic attempts.

Retires on 9 December 2026. See the migration guide for what moved where and what changes when you switch.

post/v1/webhooks/{webhook_id}/deliveries/{delivery_id}/retry

Request

  • Base URL: https://app.beel.es/api
  • URL: https://app.beel.es/api/v1/webhooks/{webhook_id}/deliveries/{delivery_id}/retry
  • Auth: HTTP bearer

Path parameters

webhook_idstring uuid required
delivery_idstring uuid required

Headers

Idempotency-Keystring

Idempotency key to prevent duplicates in sensitive operations.

  • Any unique client-generated string (e.g. an order id). A UUID also works but is not required
  • Allowed characters: letters, digits, _ and - (max 255 chars)
  • Retrying with the same key replays the first response when it was a success (2xx) or a server error (5xx): same status and body, plus the header Idempotency-Replay: true. After a 5xx, check whether the operation took effect before retrying with a new key
  • A 4xx is not stored: the key is released, so the corrected request can reuse it
  • Stored responses expire 24 hours after processing

The key is scoped per user and environment, and bound to the request body, so retrying after a network timeout replays the stored response instead of repeating the operation.

StatusCodeWhen
400INVALID_IDEMPOTENCY_KEYThe key breaks the format rules above.
409IDEMPOTENCY_KEY_PROCESSINGThe first request is still in flight. Wait for the Retry-After seconds (2) and retry with the same key.
409IDEMPOTENCY_KEY_MISMATCHThe key was already used with a different body. Use a new key.

Response

Retry result

successboolean required

Example response

{
  "success": true,
  "data": {
    "event_type": "verifactu.status.updated",
    "http_status": 200,
    "response_body_length": 29094,
    "request_headers": {
      "BeeL-Signature": "t=1741362026,v1=3c4f7a2e1b9d8e7f6a5b4c3d2e1f0a9b8c7d6e5f4a3b2c1d0e9f8a7b6c5d4e3f",
      "BeeL-Event": "verifactu.status.updated",
      "BeeL-Event-Id": "8ee6b023-c4e5-482e-93ca-dc66da2f9cb5",
      "BeeL-Delivery-Id": "b3873959-67d8-4a11-87ba-b39cc2d395fe",
      "Idempotency-Key": "8ee6b023-c4e5-482e-93ca-dc66da2f9cb5"
    }
  },
  "meta": {
    "timestamp": "2025-01-15T10:30:00Z",
    "request_id": "4bf92f3577b34da6a3ce929d0e0e4736"
  }
}

Changes

No recorded changes to this operation across all 1 revision of this API.