Skip to main content
Crypto as a Service is Anchorage Digital’s API-first platform for the full account lifecycle: create accounts for your customers, fund them with crypto or USD, trade, withdraw, and report, all under a policy engine you control. It’s built for banks, broker-dealers, fintech platforms, and wealth managers who want to offer digital assets under their own brand on top of a qualified custodian. The guides in this section walk through the v4 API flow by flow. The full contract is in the v4 API reference.
We release the v4 API iteratively, in partnership with the clients building on it. The full contract is published so you can build against it today, the sandbox is open, and the availability table shows what’s live now and what’s still being built. Endpoint definitions can still change before general availability, and your Anchorage Digital team will tell you when they do.
Building with an AI assistant? Every page here is available as Markdown (append .md to the URL) and through the Anchorage Digital docs MCP server, and there are ready-made prompts for the v4 API. See Build with AI.

Who this is for

Platforms that hold accounts for their own customers. You open an account per customer (or one omnibus for all of them), and every balance, deposit, order, and withdrawal is addressed by that account. Teams building a new integration. Build on v4. It’s the API new clients go live on.

What you can build

Open accounts

Segregated, FBO, and omnibus accounts in batches, nested into a tree.

Take deposits

A deposit address or wire instructions per account, created on demand.

Trade

Market, limit, and stop orders, booked into one account or allocated across many.

Withdraw

Batch withdrawals to trusted destinations or between accounts.

Reconcile

Balances and a double-entry transaction feed per account, plus daily reconciliation files.

Govern

Policies that allow, require sign-off for, or refuse changes.

What’s available

The contract is published in full so you can build against it, and each area is at one of three stages: Each guide repeats the table for its own endpoints, and every section about an endpoint under construction is marked inline and says so. In the API reference, groups that are under construction carry a tag. We’ll update this page as areas go live.
Live endpoints return real data once Anchorage Digital switches your sandbox organization to live responses. Until then every endpoint, live or not, returns mocked data that matches the contract, so you can build and test against it. If you’re unsure which mode your organization is in, ask your Anchorage Digital representative.

Before you can run the full flow

Some steps need Anchorage Digital to act on your sandbox organization. Ask your representative for these up front, so they don’t block you later:
  • Switching the organization to live responses, so live endpoints return real data instead of mocked data
  • Enabling account nesting, if you’ll place containers under containers
  • Enabling trading on your accounts
  • Enabling USD trusted destinations
  • Enabling the policy engine and adding its permissions to your key
  • Testnet funds for the assets you’ll test with
Two things happen on our side during a flow: each trusted destination goes through review before it reads ACTIVE, and a crypto deposit that can’t be attributed automatically is reviewed after you supply the originator.

How an integration typically goes

1

Agree your account structure with us

Before you write any code, we work with you and our compliance team to decide how your customers’ accounts are held: segregated accounts under an FBO or omnibus container, or a single pooled omnibus with your own ledger behind it. The same conversation settles whether the accounts are disclosed or undisclosed, and which KYC model applies. These choices are set in your agreement and shape everything that follows. Accounts explains the options.
2

Set up access in the sandbox

An administrator creates a permission group and an API key, and you sign your first request. Getting started covers the headers, idempotency, pagination, and error conventions that every endpoint shares.
3

Open your accounts

Create the top-level container, then open a segregated account for each customer under it, in batches, with your own identifier on each. Poll each account until it reads OPEN.
4

Set up governance

Register the keys that will approve sensitive changes, and write the policies that say which withdrawals go through on their own and which need sign-off. Then register the trusted destinations your accounts are allowed to withdraw to. See Policies and approvals and Trusted destinations.
5

Fund the accounts

Request a deposit address or wire instructions for each account and asset, and share them with the sender. Crypto deposits clear attribution before the funds are available. See Crypto deposits and USD deposits.
6

Trade and withdraw

Place orders into an account or allocate one order across several, and withdraw to the destinations you registered. See Orders and Withdrawals.
7

Reconcile

Read balances and the transaction feed per account to reconcile against your own books, and consume the daily reconciliation files once they’re delivered. See Balances, Transactions, and Reconciliation files.

Sandbox

Every guide’s examples run against the sandbox at https://api.anchorage-staging.com/v4, where the v4 API runs today. The sandbox holds testnet assets, so asset codes differ from the production codes you’ll use later. GET /v4/asset-types returns the codes your organization can use; the list the API returns is authoritative over any list in these docs. To get sandbox access, contact your Anchorage Digital representative.