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

# API reference

> Explore the reference for the Anchorage Digital v4 API, the API behind Crypto as a Service.

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.

> [!NOTE]
>
> 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](https://docs.anchorage.com/knowledge-base/platform/developers/caas/caas-overview.md#whats-available) lists each area's status, and the [Crypto as a Service guides](https://docs.anchorage.com/knowledge-base/platform/developers/caas/caas-overview.md) walk through every flow. Endpoint definitions can still change before general availability; see the [API deprecation policy](https://docs.anchorage.com/knowledge-base/api-reference/v4/api-deprecation-policy.md).

> [!TIP]
>
> 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](https://docs.anchorage.com/knowledge-base/build-with-ai/overview.md) and [Ready-made prompts](https://docs.anchorage.com/knowledge-base/build-with-ai/prompts.md#crypto-as-a-service-v4).

## Base URL

```text theme={null}
https://api.anchorage-staging.com/v4
```

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.

```http theme={null}
Api-Access-Key: YOUR_ACCESS_KEY
```

Every `POST`, `PATCH`, and `DELETE` also carries an `Idempotency-Key`, and is signed with `Api-Signature` and `Api-Timestamp`.

```http theme={null}
Idempotency-Key: 3486b413-93d3-4447-afce-2b9c9dc34a32
Api-Timestamp: 1762444800
Api-Signature: 4bf42054bf7db1f8...
```

`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](https://docs.anchorage.com/knowledge-base/platform/developers/setting-up) and [Signing requests](https://docs.anchorage.com/knowledge-base/platform/developers/request-signing.md) before sending signed requests. [Getting started](https://docs.anchorage.com/knowledge-base/platform/developers/caas/caas-getting-started.md) 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

> [card] [Accounts](https://docs.anchorage.com/knowledge-base/platform/developers/caas/caas-accounts.md)
>
> Create and manage accounts, beneficiaries, fee configurations, and compliance profiles.

> [card] [Balances and transactions](https://docs.anchorage.com/knowledge-base/platform/developers/caas/caas-transactions.md)
>
> Read balances and the transaction feed per account.

> [card] [Deposits](https://docs.anchorage.com/knowledge-base/platform/developers/caas/caas-deposits-crypto.md)
>
> Deposit instructions per asset, and deposit attribution for crypto.

> [card] [Trusted destinations](https://docs.anchorage.com/knowledge-base/platform/developers/caas/caas-trusted-destinations.md)
>
> Register and look up approved withdrawal destinations.

> [card] [Orders and withdrawals](https://docs.anchorage.com/knowledge-base/platform/developers/caas/caas-orders.md)
>
> Place and track orders, and move funds out.

> [card] [Policy engine](https://docs.anchorage.com/knowledge-base/platform/developers/caas/caas-policies.md)
>
> Register approval keys, write policies, and endorse pending actions.


## Related topics

- [API Reference](https://docs.anchorage.com/knowledge-base/porto/api-reference/v3/introduction.md)
- [API deprecation policy](https://docs.anchorage.com/knowledge-base/api-reference/v4/api-deprecation-policy.md)
- [API Changelog](https://docs.anchorage.com/knowledge-base/porto/api-reference/changelog.md)
