---
title: "Retry a failed webhook"
method: POST
path: "/v4/subscription/webhook/{id}/retry"
tags: ["Notifications"]
---

# Retry a failed webhook

`POST /v4/subscription/webhook/{id}/retry`

## Request

- Base URL: `https://api.tatum.io`
- URL: `https://api.tatum.io/v4/subscription/webhook/{id}/retry`
- Auth: API key in header `x-api-key`

/v4/subscription/webhook/{id}/retry

Retry a failed webhook by re-queueing it for delivery. Only webhooks in the failed state can be retried.

The retry is delivered with the current configuration, not the one used for the original attempt: it goes to the alert's current URL and is signed with the current HMAC secret (unsigned if HMAC was disabled since). To deliver to a different URL or with a different secret, update the alert or the HMAC configuration first, then retry.

## Path parameters

- `id` string, required

## Response `204`

Webhook was queued for retry.

## Other responses

- `400`: Invalid webhook ID or webhook is not in failed state.
- `401`: Unauthorized. Not valid or inactive subscription key present in the HTTP Header.
- `404`: Webhook was not found for the authenticated API key.
- `409`: Webhook is already queued for retry, its alert is paused (resume the alert before retrying), or the product's usage limit is exceeded.
- `410`: The webhook's alert was deleted or its payload is no longer available.
- `500`: Internal server error. There was an error on the server during the processing of the request.

---

[API](https://skmtc.dev/tatum/apis/blockchain-notifications.md) - [All operations](https://skmtc.dev/tatum/apis/blockchain-notifications/llms.txt) - [OpenAPI document](https://skmtc.dev/tatum/apis/blockchain-notifications/revisions/925883906ce5?raw)