The Notifications API lets you subscribe to on-chain events for specific wallet or token addresses and receive real-time webhook notifications without polling the blockchain. When a relevant transaction occurs, Fuse posts the event payload to your registered webhook URL. The API supports native FUSE transfers, ERC20 token transfers, and ERC-721/ERC-1155 NFT transfers.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/fuseio/fuse-docs/llms.txt
Use this file to discover all available pages before exploring further.
Base URL
Authentication
All requests require both a public API key and a secret API key as query parameters:Event types
When creating a webhook, set theeventType field to one of these values:
| Value | Events received |
|---|---|
ALL | All transfer types |
FUSE | Native FUSE transfers only |
ERC20 | ERC20 token transfers only |
ERC721 | ERC-721 and ERC-1155 NFT transfers |
Webhook IP allowlist
To verify that notifications originate from Fuse, you can allowlist these IP addresses on your server:Retry logic
Failed webhook deliveries (non-200 responses or connection failures) are retried up to 6 times:| Retry | Delay after previous attempt |
|---|---|
| 1 | 15 seconds |
| 2 | 1 minute |
| 3 | 10 minutes |
| 4 | 1 hour |
| 5 | 1 day |
| 6 | 1 day |
POST /webhook
Creates a new webhook associated with your project.Request parameters
Your public API key.
Your secret API key.
Request body
The HTTPS URL where event payloads will be delivered.
Type of events to subscribe to. One of:
ALL, FUSE, ERC20, ERC721.Your project ID. Find it in the URL of your project page in the Fuse Console.
Response
Unique identifier for the newly created webhook.
The URL registered for event delivery.
The event type subscription.
The project this webhook is associated with.
Example
PUT /webhook
Updates an existing webhook’s URL or event type.Request parameters
Your public API key.
Your secret API key.
Request body
The ID of the webhook to update.
New HTTPS URL for event delivery.
New event type subscription. One of:
ALL, FUSE, ERC20, ERC721.Example
GET /webhook/
Retrieves details of a specific webhook.Request parameters
Your public API key.
Your secret API key.
The ID of the webhook to retrieve.
Example
DELETE /webhook/
Deletes a webhook. After deletion, no further events will be delivered to the associated URL.Request parameters
Your public API key.
Your secret API key.
The ID of the webhook to delete.
Example
GET /webhooks/
Returns all webhooks associated with a project.Request parameters
Your public API key.
Your secret API key.
The project ID to list webhooks for.
Example
POST /webhook/add-addresses
Adds wallet or token addresses to an existing webhook. Once added, events involving those addresses will trigger the webhook.Request parameters
Your public API key.
Your secret API key.
Request body
The ID of the webhook to add addresses to.
Array of wallet or token contract addresses to subscribe to.
Example
Event payload examples
Native FUSE transfer
ERC20 token transfer
Thevalue field includes the token’s decimals, given in tokenDecimals.
ERC721 NFT transfer
NFT transfers includetokenId instead of value.
If you subscribe to both a wallet address and a token address that both appear in the same event, you may receive two deliveries for that event. Differentiate them using the
addressType field: Wallet for subscribed wallet addresses, Token for subscribed token addresses.