Skip to main content
The Wallet API is the full wallet backend over REST. Reads take a plain address, transaction preparation returns an unsigned transaction to whatever signer you use, and broadcast accepts any signed transaction. There is no wallet registration step, and using WalletSuite MPC is a choice, not a requirement. Every call runs on the same x-api-key credential. See Credentials & Authentication.

​
Sign with your own keys

The transaction flow is three steps, and signing stays entirely on your side:
  1. POST /api/txs/prepare-sign with chain, from, to, and amount. WalletSuite computes everything the transaction needs: nonce, fees, sequencing, every chain-specific field, and runs a simulation check. You receive the unsigned transaction, ready for signature.
  2. Sign it in your own infrastructure: your HSM, KMS, or key management scheme. WalletSuite never sees key material.
  3. POST /api/txs/send with the signed transaction. WalletSuite broadcasts it. Track it by hash with GET /api/txs/status/{hash} or react to webhooks.
The same flow works with WalletSuite MPC or an external signer producing the signature. The full lifecycle is documented in Transaction Lifecycle.

​
What the API covers

Balances & assets

Native and token balances for any address, token prices by symbol or contract, and asset metadata and info.

Transactions & fees

Fee calculation, transaction simulation, signer-agnostic preparation, broadcast, and status by hash.

Swaps

One quote request routed across integrated providers, returning routes ranked best first, with a signing-ready build step.

Webhooks

Signed notifications when a deposit lands on a watched address, retried until your endpoint confirms.
Browse every endpoint with runnable examples in the API Reference.

​
Chains

The Wallet API is chain-agnostic: every chain is served through one normalized schema, so a balance, a fee quote, or a transaction reads the same shape whether it’s on Ethereum, Solana, Bitcoin, or Tron — no per-chain branching, no chain-specific SDKs. You write your integration once; adding a chain is a configuration change, not an integration project. The API covers 80+ chains today — see Supported Chains for the current list.

​
Simulation

prepare-sign runs a simulation check as part of preparation: you know whether a transaction will succeed before anything is signed and before any gas is spent. Failed transactions get caught upfront, not on chain.