> ## 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.

# API Reference

> Authenticate and make your first request against the WalletSuite REST API.

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 [hosted agent platform](/ai-agents/overview) and the [SDK](/sdk/overview); all three compose with the same signing layer (non-custodial MPC threshold signing, or external BYO via the SDK). See [Security Overview](/security/overview#trust-model) for the cross-surface trust model.

<Tip>
  Prefer typed helpers? Use the [SDK](/sdk/quick-start) instead. Building an AI agent? See the [Agent Platform Quickstart](/ai-agents/quickstart).
</Tip>

## 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

<Steps>
  <Step title="Get your API key">
    Request an API key from your WalletSuite point of contact. Once you receive it, store it as an environment variable:

    ```bash theme={null}
    export WALLETSUITE_API_KEY="your-api-key"
    ```
  </Step>

  <Step title="Send an authenticated request">
    Pass your key in the `x-api-key` header on every request. All requests must use HTTPS.

    ```bash theme={null}
    curl -X GET "https://api.walletsuite.io/api/blocks/latest?chain=ethereum" \
      -H "x-api-key: $WALLETSUITE_API_KEY"
    ```
  </Step>

  <Step title="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](/getting-started/prerequisites/rate-limits) for retry guidance.
  </Step>
</Steps>

## Next steps

<CardGroup cols={2}>
  <Card title="Credentials & Authentication" icon="key" href="/getting-started/prerequisites/credentials-and-authentication">
    The `x-api-key` header in full, plus authentication error responses.
  </Card>

  <Card title="Rate Limits" icon="gauge-high" href="/getting-started/prerequisites/rate-limits">
    Quota enforcement and how to handle `429` responses.
  </Card>
</CardGroup>