Skip to main content
The v4 API is the API behind Crypto as a Service. It covers accounts and their tree, balances and transactions, deposit instructions and attributions, trusted destinations, orders and allocations, withdrawals, and the policy engine, with account updates, beneficiaries, customer onboarding, compliance profiles, fee configurations, interest enrollment, approval groups, and endorsements still under construction.
We release the v4 API iteratively, in partnership with the clients building on it. The whole contract is published so you can build against it in the sandbox today. The groups tagged under construction in the sidebar return mocked data only, so you can code to their shape before they go live. What’s available lists each area’s status, and the Crypto as a Service guides walk through every flow. Endpoint definitions can still change before general availability; see the API deprecation policy.
Building with an AI assistant? Connect the Anchorage Digital docs MCP server or start from the Crypto as a Service prompts. See Build with AI and Ready-made prompts.

Base URL

The sandbox is the only environment the v4 API runs in today. Production access comes with general availability.

Authentication

Every request carries the Api-Access-Key header.
Every POST, PATCH, and DELETE also carries an Idempotency-Key, and is signed with Api-Signature and Api-Timestamp.
Api-Signature is a hex-encoded Ed25519 signature over timestamp_epoch_seconds + uppercase(http_method) + request_path + request_body, and Api-Timestamp is the same timestamp in Unix epoch seconds. Read Setting up and Signing requests before sending signed requests. Getting started covers idempotency, batch results, and the If-Match concurrency header.

Notifications

Webhooks for the v4 API are coming soon. Until then, poll the read endpoints to follow an object to its final state.

Pagination and errors

List endpoints accept limit (page size) and after (cursor), and return page.endCursor to continue from. Errors carry a JSON body with a human-readable message. Batch endpoints return a result per item instead, with status: ERROR and an error on the items that failed.

Endpoint areas

Accounts

Create and manage accounts, beneficiaries, fee configurations, and compliance profiles.

Balances and transactions

Read balances and the transaction feed per account.

Deposits

Deposit instructions per asset, and deposit attribution for crypto.

Trusted destinations

Register and look up approved withdrawal destinations.

Orders and withdrawals

Place and track orders, and move funds out.

Policy engine

Register approval keys, write policies, and endorse pending actions.