How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Anchorage Digital

Anchorage Digital Wallets API

A vault has one or more wallets. Each wallet is a collection of one or more addresses depending on the asset type. A wallet is created for a particular blockchain network, e.g. Bitcoin, Ethereum, etc.### BalancesDepending on the blockchain network of the wallet, a wallet may hold one or more asset types. An asset in a wallet has an `availableBalance` and a `totalBalance`. The `availableBalance` is the balance that is available to be withdrawn, held, or transferred. The `totalBalance` may contain funds that are held, in-progress, or locked for activities like voting.### AddressesA wallet is a collection of one or more addresses depending on the asset type. The `depositAddress` contains the last address to be provisioned to that wallet. For UTXO-based assets this address could change as new deposit addresses are provisioned. For account-based assets, this address will not change as only one address may be provisioned per wallet. To see all addresses for an asset, use the [Addresses endpoint](#tag/Addresses).### Default WalletsEach asset type within a vault has a default wallet that is used for a particular asset when only the vault is specified. For example, a transfer between two vaults will take the asset from the default wallet for that asset in the sending vault and send it to the default wallet for that asset in the destination vault. Each wallet has a `isDefault` flag that indicates whether it is the default wallet.### Maximum Allowed Wallets and Creation ConstraintsWe have a constraint of 10,000 wallets per asset and defined a creation limit of 10 wallets per asset per 30 minutes interval. Theses contraints are imposed at the organization level.

Documentation Provider Profile APIs.io OpenAPI GitHub

Anchorage Digital Wallets API is one of 28 APIs that Anchorage Digital publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Wallets. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 11 operations across 10 paths, and defines 34 schemas. It is described by OpenAPI 3.2.0, at version 2.0.0.

Requests are made against a single base URL, https://api.anchorage-staging.com/v2.

11 operations 10 paths 34 schemas 8 GET3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0.0
Base URL
https://api.anchorage.com/v2
Authentication
API Key
Contact
api@anchorage.com
Resource Areas
1

Authentication & Security 1

Anchorage Digital Wallets API declares 1 security scheme for authenticating requests. An API key is passed in the header as Api-Access-Key (Api-Access-Key). By default, every request must be authenticated.

  • Api-Access-Key — An API key associated with a security role

Paths & Operations 11

Across 10 paths, the API surfaces 11 operations — 8 GET, 3 POST. Each is listed below with its method, path, parameters, and response codes.

Wallets 11

A vault has one or more wallets. Each wallet is a collection of one or more addresses depending on the asset type. A wallet is created for a particular blockchain network, e.g. Bi…

GET
/vaults/{vaultId}/wallets
List all wallets for a vault
getVaultWallets 6 params → 200400401403404429500
POST
/vaults/{vaultId}/wallets
Create a new wallet in a vault
createVaultWallet 1 param body → 200400401403404429500
GET
/wallets
List all wallets for all vaults
getWallets 7 params → 200400401403404429500
GET
/wallets/{walletId}
Wallet details for a wallet
getWallet 2 params → 200400401403404429500
POST
/wallets/{walletId}/activate
Activate an existing wallet on additional networks
activateWallet 1 param body → 200400401403404429500
GET
/wallets/{walletId}/staking/rewards
Staking rewards for a wallet
getWalletRewards 5 params → 200400401403404429500
GET
/wallets/{walletId}/staking/positions
Staking positions for a wallet
getWalletPositions 4 params → 200400401403404429500
POST
/batch/wallets
Create or Activate Wallets Batch
createWalletsBatch body → 202400401403429500
GET
/batch/wallets/{batchId}
Get Wallets Batch Status
getWalletsBatchStatus 1 param → 200400401403404429500
GET
/wallets/{walletId}/rewards
Get Wallet Rewards (Per-Event)
getWalletRewards 7 params → 200400401403404429500
GET
/wallets/{walletId}/daily-rewards
Get Daily Wallet Rewards (Aggregated)
getDailyWalletRewards 5 params → 200400401403404429500

Schemas 34

The contract defines 34 schemas that model the data the API accepts and returns. The most detailed are WalletDetails (13 properties), WalletPositionsDetails (9 properties), DepositInstruction (8 properties), AssetDetailsForWallet (7 properties). Each schema is shown below with its type and property counts.

VaultsWalletResponse
object
1 property 1 required
ResourceType
string
The type of the resource being referenced. Note that the VAULT type has been deprecated and WALLET should be used instead.
DepositInstruction
object
The deposit instructions for fiat wallets. Crypto wallets use a deposit address instead.
8 properties 7 required
WalletRewardsResponse
object
2 properties 2 required
BatchStatusResponse
object
Status of a batch operation
2 properties 2 required
ErrorDetails
object
2 properties 2 required
Amount_2
object
Combines an asset identifier with a decimal string value
2 properties 2 required
ActivateWalletResult
object
4 properties 2 required
WalletsResponse
object
2 properties 2 required
ActivateWalletRequest
object
2 properties
WalletRewardsDetails
object
4 properties 4 required
WalletRewardsResponse_2
object
Response containing daily rewards over a date range for a specific reward type
1 property 1 required
CreateWalletsBatchRequest
Request to create or activate multiple wallets in a batch operation. A wallet exists on exactly one network. Supports three mutually exclusive patterns: 1. Bat…
ErrorDetails_2
object
1 property 1 required
SignedAddressForWallet
object
The deposit address for crypto wallets. Fiat wallets use deposit instructions instead.
6 properties 4 required
Page
object
Pagination info
1 property
WalletRewardsListResponse
object
2 properties 2 required
Amount
object
An amount of a crypto-asset represented by quantity, assetType, current unit price and current USD value. Fee amounts will be estimates if a transaction is not…
4 properties 2 required
VaultsWalletsRequest
object
5 properties 1 required
AddressGenerationType
string
Address format type for Bitcoin-like blockchains. DEFAULT - Network's default format (P2SH-P2WPKH for most networks) BITCOINLIKEP2PKH - Legacy Pay-to-Public-Ke…
WalletDetails
object
13 properties 9 required
VaultsWalletsResponse
object
2 properties 2 required
ActivateWalletResponse
object
1 property 1 required
CreateBatchResponse
object
Response from creating a batch operation
1 property 1 required
RewardEntry
object
A single reward entry with type, date, amount, and optional transaction and staking position references
5 properties 3 required
Page_2
object
Pagination info
1 property
BatchActivateWalletsFromVaultRequest
object
Activate all wallets in a vault/network for new target networks. For each wallet in the vault on the source network, creates new wallets on the target networks…
5 properties 3 required
WalletPositionsResponse
object
2 properties 2 required
ErrorType
string
The type of error returned.
AssetDetailsForWallet
object
7 properties 3 required
DailyRewardEntry
object
Reward amount for a single day
3 properties 2 required
BatchActivateWalletsFromListRequest
object
Activate specific wallets for new target networks. Creates new wallets (one per source × target combination) that share keys with the source wallets.
4 properties 2 required
BatchCreateWalletsRequest
object
Create wallet sets with fresh keys across multiple networks. A wallet exists on exactly one network.
6 properties 3 required
WalletPositionsDetails
object
9 properties 9 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

anchorage-wallets-api-openapi.yml Raw ↑

Other APIs Anchorage Digital publishes across the network.

Anchorage Digital Addresses API
AE Profile APIs.io
Anchorage Digital AML API
AE Profile APIs.io
Anchorage Digital API Key API
AE Profile APIs.io
Anchorage Digital Asset Types API
AE Profile APIs.io
Anchorage Digital Asset Types & Networks API
AE Profile APIs.io
Anchorage Digital Atlas Settlement Network API
AE Profile APIs.io
Anchorage Digital Balances API
AE Profile APIs.io
Anchorage Digital Collateral Management API
AE Profile APIs.io
Anchorage Digital Deposit Attribution API
AE Profile APIs.io
Anchorage Digital Fiat Banking Operations API
AE Profile APIs.io
Anchorage Digital Onboarding API
AE Profile APIs.io
Anchorage Digital Stablecoins API
AE Profile APIs.io
#Wallets
← Back to A APIs
API Details
ID
anchorage:anchorage-wallets-api
Base URL
https://api.anchorage.com/v2
Docs
https://docs.anchorage.com/knowledge-base/api-reference/introduction
Provider
Anchorage Digital
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=anchorage-wallets-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/anchorage-wallets-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of Anchorage Digital Wallets API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.