The FuseBox platform provides a collection of REST APIs that cover everything from smart wallet management and token balances to DEX trading, blockchain analytics, webhook notifications, and token staking. All APIs share a single base URL and use an API key for authentication, so once you have your key you can start calling any endpoint in the suite.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
All API calls are made over HTTPS to the production server:https://api.fuse.io/api/v2/smart-wallets and the Balances API at https://api.fuse.io/api/v0/balances.
Authentication
Every request must include your public API key. Pass it as a query parameter namedapiKey:
API-SECRET request header, alongside the apiKey query parameter. The Smart Wallets API issues a short-lived JWT after the initial authentication call; subsequent calls to protected endpoints use a Bearer token in the Authorization header.
Get your API keys from the Fuse Console.
All API calls must be made over HTTPS. HTTP requests will be rejected.
Available APIs
Smart Wallet API
Create and manage ERC-4337 smart contract wallets. Authenticate users, relay gasless transactions, and fetch wallet action history.
Balances API
Query ERC-20 fungible token balances and ERC-721/ERC-1155 NFT holdings for any wallet address on the Fuse network.
Trade API
Integrate DEX trading powered by Voltage Finance. Fetch token prices, price change data, and obtain swap quotes or indicative prices.
Notification API
Subscribe to real-time blockchain events via webhooks. Monitor native FUSE transfers, ERC-20 transfers, and NFT transfers for any address.
Explorer API
Query blockchain data including transactions, balances, blocks, token analytics, and smart contract information on Fuse.
Staking API
Manage token staking on the Fuse network. Retrieve staking options, stake or unstake tokens, and query staked balances by wallet.
Common response patterns
All APIs return JSON responses. Successful responses use standard HTTP 2xx status codes. Errors follow a consistent shape:| HTTP status | Meaning |
|---|---|
200 | Request succeeded |
201 | Resource created successfully |
400 | Bad request — check your request body or query parameters |
401 | Unauthorized — missing or invalid JWT token |
403 | Forbidden — invalid or missing API key |
docs array along with pagination metadata. Cursor-based endpoints (such as the NFT Balances endpoint) return a nextCursor field that you pass in the next request to fetch the following page.