Missed webhook notifications can occur due to various issues such as temporary downtime, connectivity problems, or unexpected errors in your webhook handler. These issues can prevent your server from acknowledging or processing events sent by Fireblocks.
To ensure no critical events are lost, Fireblocks provides API endpoints to resend webhook notifications as needed.
Resend a single notification
The Resend notification by ID endpoint lets you resend a single notification by its unique notificationId identifier. It is ideal when you want to troubleshoot or ensure the delivery of a specific event, such as a transaction update or status change.
Example use case
If your server fails to process a specific transaction notification, you can use this endpoint to retry only that notification, minimizing unnecessary retries.
Resend multiple notifications by resource
The Resend notifications by resourceId endpoint lets you resend multiple notifications for all failed webhooks associated with a specific resourceId. This is particularly useful when you need to retry notifications for a specific resource, such as a vault account or transaction, after resolving server-side issues.
Example use case
If your webhook server missed updates for a specific transaction due to an outage, you can use this endpoint to retrieve all missed notifications related to that transaction.
Recover from downtime
Under development
This endpoint is currently under development and will be released soon.
This endpoint resends all failed webhook notifications for a given webhook. It is a comprehensive solution for situations where your server has experienced extended downtime or a widespread failure. You can set the resend duration for up to 24 hours.
Example use case
If your webhook server was offline for an hour due to a deployment or network issue, you can use this endpoint to ensure all missed events are resent.