> ## Documentation Index
> Fetch the complete documentation index at: https://docs.walletsuite.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Wallet API

> One REST API for every wallet operation: balances, prices, asset metadata, history and status, fee calculation, transaction preparation, simulation, swaps, webhooks, and broadcast across 80+ chains. Works with any signer.

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](/getting-started/prerequisites/credentials-and-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](/webhooks/overview).

The same flow works with [WalletSuite MPC](/mpc/overview) or an external signer producing the signature. The full lifecycle is documented in [Transaction Lifecycle](/core-concepts/transaction-lifecycle).

## What the API covers

<CardGroup cols={2}>
  <Card title="Balances & assets" icon="wallet" href="/getting-started/api-reference/overview">
    Native and token balances for any address, token prices by symbol or contract, and asset metadata and info.
  </Card>

  <Card title="Transactions & fees" icon="arrow-right-arrow-left" href="/getting-started/api-reference/overview">
    Fee calculation, transaction simulation, signer-agnostic preparation, broadcast, and status by hash.
  </Card>

  <Card title="Swaps" icon="rotate" href="/getting-started/api-reference/overview">
    One quote request routed across integrated providers, returning routes ranked best first, with a signing-ready build step.
  </Card>

  <Card title="Webhooks" icon="bolt" href="/webhooks/overview">
    Signed notifications when a deposit lands on a watched address, retried until your endpoint confirms.
  </Card>
</CardGroup>

Browse every endpoint with runnable examples in the [API Reference](/getting-started/api-reference/overview).

## 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](/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.