Anchorage Digital Subaccounts 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 Subaccounts. The published artifact set on APIs.io includes an OpenAPI specification.
This API exposes
17 operations
across 12 paths,
and defines 61 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.
17 operations12 paths61 schemas2 DELETE9 GET1 PATCH5 POST
Metadata
The identity and technical contract details declared by the specification.
Anchorage Digital Subaccounts 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 17
Across 12 paths, the API surfaces 17 operations — 2 DELETE, 9 GET, 1 PATCH, 5 POST. Each is listed below with its method, path, parameters, and response codes.
Subaccounts 17
These endpoints allow the organization to manage subaccounts.
The contract defines 61 schemas that model the data the API accepts and returns. The most detailed are SubaccountsDetails (12 properties), AccruedFeeType (7 properties), ListSubaccountWithdrawalsObject (7 properties), CreateSubaccountTransaction (6 properties). Each schema is shown below with its type and property counts.
FeeCalculationStateType
string
SubaccountType
string
Type of the subaccount
CreateSubaccountBillingChargesResponse
object
1 property1 required
CreateFundingAllocationsRequest
object
Details of the allocations to create
2 properties2 required
ProgramSigner
object
3 properties3 required
TransactionIdResponse
object
1 property
WithdrawalBankInfo
object
Information needed to trigger the wire transfer
4 properties1 required
GetSubaccountWithdrawalObject
object
3 properties
ListSubaccountWithdrawalsObject
object
7 properties
DestinationAddress
object
Information related to the Address of the Benificiary
6 properties4 required
AssetAmount
object
2 properties2 required
UpdateFeeDetailType
object
4 properties2 required
CancelSubaccountBillingChargeResponse
object
1 property1 required
CreateFundingAllocationsResponse
object
2 properties1 required
UpdateSubaccountResponse
object
1 property1 required
SubaccountTransactionAmount
object
2 properties
SubaccountTransactionStatus
string
A string describing the status of the given transaction POSTED - This transaction has been completed and is confirmed on the blockchain. CANCELED - This transa…
SubaccountTransactionEntry
object
2 properties
ErrorDetails
object
2 properties2 required
CreateFundingAllocation
object
4 properties4 required
UpdateSubaccountRequest
object
Details of the subaccount to open for the customer
4 properties
FeeDetailType
object
4 properties4 required
SubaccountsDetails
object
12 properties8 required
ListSubaccountWithdrawalsResponse
object
2 properties1 required
Balance
object
2 properties
SubaccountTransactionsByIdResponse
object
2 properties1 required
CreateSubaccountBillingChargesRequest
object
Details of the billing charge to create
4 properties3 required
CreateFeeDetailType
object
3 properties1 required
SubaccountTransactionType
string
A string describing the type of the given transaction DEPOSIT - Deposit transaction WITHDRAWAL - Withdrawal transaction TRADE - Trade transaction MANAGEMENTFEE…
SubaccountStatus
string
Status of the subaccount
SubaccountCustomer
object
Unique Identifier and role for the program customer in subaccount
2 properties
GetSubaccountWithdrawalResponse
object
1 property1 required
BankInfoResponse
object
1 property
SubaccountWalletResponse
object
2 properties
SubaccountWithdrawalResponse
object
1 property1 required
Page
object
Pagination info
1 property
CreateFeeType
string
CreateSubaccountTransaction
object
Details of a transaction to create
6 properties5 required
BeneficiaryGroup
array
SubaccountsResponse
object
2 properties1 required
CancelSubaccountWithdrawalResponse
object
1 property1 required
BalanceDetails
object
5 properties
CreateSubaccountTransactionResponse
object
1 property1 required
SubaccountSubType
string
SubType of the subaccount, may not always apply
SubaccountTransactionsResponse
object
2 properties1 required
CancelSubaccountWithdrawalObject
object
1 property
CreateSubaccountTransactionRequest
object
Details of the transactions to create
1 property1 required
RoutingDetails
object
4 properties2 required
Beneficiary
object
3 properties3 required
BeneficiaryType
string
SubaccountIdResponse
object
1 property1 required
CreateSubaccountWithdrawalRequest
object
Details of the withdrawal to create for the subaccount
2 properties2 required
ErrorType
string
The type of error returned.
FeeType
string
SubaccountCustomers
array
List of account owners with their respective roles (can only be changed during onboarding)
ProgramSignerGroup
array
CreateSubaccountRequest
object
Details of the subaccount to open for the program customer
3 properties3 required
CreateSubaccountWithdrawalResponse
object
1 property1 required
SubaccountTransaction
object
6 properties4 required
AccruedFeeType
object
7 properties6 required
CreateSubaccountResponse
object
1 property1 required
Specification
The full machine-readable OpenAPI contract behind this narrative.
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.
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 Subaccounts 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.