Skip to main content
The WalletSuite REST API gives you direct HTTPS access to every wallet operation - balances, prices, fees, transaction preparation, broadcasting, and more. It is one of three WalletSuite surfaces alongside the MCP server and the SDK; all three compose with the same signing layer (MPC, or external BYO via the SDK). See Security Overview for the cross-surface trust model.
Prefer typed helpers? Use the SDK instead. Building an AI agent? See the MCP Quickstart.

​
Built for

Teams who need REST access to wallet operations from any language or stack — no SDK dependency, no agent layer. Common shapes: server-side backends handling multi-chain payments, internal treasury or ops dashboards, and embedded Web3 features inside existing fintech or commerce products.

​
What you can build

  • Native and token balance queries with fiat valuation
  • Price, fee-quote, transaction status, and history queries across supported chains
  • Asset catalogs and name-service resolution (ENS, UNS)
  • NFT ownership and token allowance queries
  • Transaction preparation — payload construction, fee estimation, and simulation
  • Broadcast pre-signed transactions to supported chains
  • Staking and swap metadata queries on supported chains
  • Real-time webhook subscriptions with signed event delivery across supported chains

​
Make your first API request

1

Get your API key

Request a Pilot API key from your WalletSuite point of contact. Once you receive it, store it as an environment variable:
export WALLETSUITE_API_KEY="your-api-key"
2

Send an authenticated request

Pass your key in the x-api-key header on every request. All requests must use HTTPS.
curl -X GET "https://api.walletsuite.io/api/blocks/latest?chain=ethereum" \
  -H "x-api-key: $WALLETSUITE_API_KEY"
3

Handle the response

A successful response returns 200 OK with a JSON body. If you receive 401 or 403, check that your key is valid and correctly set in the header. If you receive 429, you have exceeded your rate limit — see rate limits for retry guidance.

​
Next steps

Credentials & Authentication

The x-api-key header in full, plus authentication error responses.

Rate Limits

Quota enforcement and how to handle 429 responses.