---
title: "Retry an account webhook delivery"
method: POST
path: "/accounts/{account}/webhooks/{webhook}/deliveries/{delivery}/retry"
tags: ["Account"]
---

# Retry an account webhook delivery

`POST /accounts/{account}/webhooks/{webhook}/deliveries/{delivery}/retry`

## Request

- Base URL: `https://api.factuarea.com/v1`
- URL: `https://api.factuarea.com/v1/accounts/{account}/webhooks/{webhook}/deliveries/{delivery}/retry`
- Auth: one of:
  - HTTP bearer
  - API key in header `X-API-Key`

Re-arm a failed delivery: the SAME delivery returns to `pending` and is sent again with the current signing secret.
- Only `failed` and `failed_permanently` can be retried; others return 422 subcode `account_webhook_retry_not_allowed`.
- Returns 202; requires a live key and an `Idempotency-Key`; 404 `webhook_delivery_not_found`.

## Path parameters

- `account` string, uuid, required
- `webhook` string, uuid, required
- `delivery` string, uuid, required

## Headers

- `Idempotency-Key` string, required
- `Factuarea-Version` string, date

## Response `202`

The delivery was re-armed and queued: the SAME delivery goes back to `pending` and is sent again with the current signing secret. `data.id` is that delivery; read its outcome with the delivery detail.

- object
  - `data` object, required
    - `id` string, uuid, required: Opaque identifier (UUID v7) of the re-armed delivery: the `{delivery}` of the path.
    - `object` 'account_webhook_delivery', required: Always `account_webhook_delivery`.
    - `status` 'queued', required: Always `queued`: the delivery was accepted and is sent asynchronously.

## Other responses

- `400`: `parameter_unknown` with `subcode` `retired_active_profile_header`: the retired `X-Active-Profile` header was sent; the company goes in the path. `parameter_invalid_format` on `Factuarea-Version`: the header is not a `YYYY-MM-DD` date. `unsupported_api_version`: the `Factuarea-Version` date is not a supported version.
- `401`: Missing or invalid API key.
- `403`: The request is authenticated but not allowed: the API key lacks the required scope (`insufficient_scope`), the plan does not include the public API or this feature (`addon_not_active`, `feature_not_available_in_plan`), or the module is not available with a test key (`module_not_available_in_sandbox`).
- `404`: The requested resource does not exist or belongs to another company.
- `422`: Validation failed — e.g. the API key plan limit was reached, or an invoice language outside the allowed catalog (`es`, `en`, `ca`). The `error.param` field identifies which input is invalid, if any.
- `429`: Rate limit exceeded. Retry after the duration in `Retry-After`.
- `500`: Unexpected server error.

---

[API](https://skmtc.dev/factuarea/apis/factuarea-public-api.md) · [All operations](https://skmtc.dev/factuarea/apis/factuarea-public-api/llms.txt) · [OpenAPI document](https://skmtc.dev/factuarea/apis/factuarea-public-api/revisions/718e77934422?raw)