Replay webhook delivery
Re-queue a webhook delivery. A new delivery attempt is created (with attempt: 1) for the same event/endpoint pair.
Request
- Base URL: https://api.factuarea.com/v1
- URL: https://api.factuarea.com/v1/companies/{company}/webhook-endpoints/{webhook_endpoint}/deliveries/{delivery}/replay
- Auth: one of:
- HTTP bearer
- API key in header X-API-Key
Path parameters
Public identifier (UUID v7) of the company. Get it from GET /v1/me (data.scope[].id).
Public identifier (UUID v7) of the webhook endpoint.
Public identifier (UUID v7) of the webhook delivery.
Headers
Client-generated opaque key (up to 255 characters; UUID v7 recommended) that makes retries safe: the first response is cached and replayed for repeats without re-executing the mutation. Reusing a key with a different body returns 422 idempotency_key_reused; the values of secret fields (password, secret…) count as part of the body, so retrying with a corrected secret under the same key is a different request, never the replay of the earlier answer. See the Idempotency guide. Required on this operation: repeating it delivers an effect that cannot be taken back (an email sent, a file generated, a third-party call, a charge), so a request without this header is rejected with 422 idempotency_key_required before any business logic runs.
Pin the API version (YYYY-MM-DD, Stripe-style date versioning) for this request; omit to use the key's pinned version, or the latest if none. Unsupported version → 400 unsupported_api_version; malformed → 400 parameter_invalid_format. The effective version is echoed in the Factuarea-Version response header. See the Versioning guide.
Response
Example response
{
"data": {
"new_delivery_id": "01931b3e-7c4a-7f2e-9a8b-3c5d6e7f8a0c",
"webhook_endpoint_id": "01931b3e-7c4a-7f2e-9a8b-3c5d6e7f8a0b",
"status": "queued"
}
}Changes
No recorded changes to this operation across all 1 revision of this API.