Skip to main content
Deprecation noticeWebhooks v1 has been in soft deprecation since June 15, 2026: it receives no fixes or enhancements, and issue resolution is not guaranteed. Starting October 5, 2026, v1 is being shut down permanently in phases, with all workspaces affected by October 28, 2026. Once shut down, v1 stops delivering notifications and cannot be restored. Fireblocks is not responsible for missed or delayed notifications or any disruption resulting from continued use of Webhooks v1. Upgrade to Webhooks v2 now via the Developer Center in the Fireblocks Console. For upgrade steps and event mapping, see the Webhooks v2 Migration Guide.

Overview

Webhooks provide real-time notifications for events happening within your Fireblocks workspace, such as incoming and outgoing transactions, transaction status updates, and the addition of new vault accounts, contract wallets, internal wallets, or external wallets. By configuring webhooks, you can ‘listen’ for these events at your chosen URL, ensuring that all relevant event types are broadcast to your designated endpoint. Using webhooks offers several benefits, particularly for event-driven development. They enable immediate awareness of critical events, allowing your systems to respond quickly and automatically to changes in your workspace. This real-time monitoring enhances operational efficiency, as it can trigger automated workflows, updates, or alerts based on the specific events received. Webhooks also facilitate seamless integration with your existing applications, enabling more dynamic and responsive interactions between your Fireblocks workspace and other platforms. When implementing webhooks, consider the reliability and scalability of the receiving endpoint. Ensure that your system can handle the volume of incoming events and process them efficiently. If notifications are missed due to any issue, Fireblocks offers the following API endpoints for resending webhook notifications: Key Features:
  • Event Ordering - Webhook events are sent in order with a 10-second delay.
  • Retry Logic - Missed Webhooks are retried every 5, 15, 35, 75, 155, 315, 635, 1275, 2555 (in seconds).

Payload Structure

We have a standard payload structure that we implement throughout, as shown below: Below is a sample of the payload response:

Event Types

IP Whitelisting

Whitelisting Webhook IP addresses is optional but recommended. Webhooks are sent from the following IPs:
  • US environment: 3.134.25.131
  • EU environment: 3.72.125.45, 18.184.217.45, 18.198.71.192