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 Transactions API

Transactions include all of the blockchain actions that affect your vault balances, such as withdrawals, deposits, transfers, and participation actions. Each transaction may have a corresponding blockchain transaction.Only transactions that are final will be returned. This includes all successful transactions as well as unsuccessful transactions where a blockchain fee was paid.Deposits, once confirmed on-chain, are subject to collection of originator data. Check the [Deposit Attribution](#tag/Deposit-Attribution) section for details.

Documentation Provider Profile APIs.io OpenAPI GitHub

Anchorage Digital Transactions 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 Transaction. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 8 operations across 8 paths, and defines 39 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.

8 operations 8 paths 39 schemas 3 GET5 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 Transactions 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 8

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

Transactions 8

Transactions include all of the blockchain actions that affect your vault balances, such as withdrawals, deposits, transfers, and participation actions. Each transaction may have…

POST
/transactions/withdrawal
Create a withdrawal request
createWithdrawal 2 params body → 201400401403404409429500
GET
/transactions
List transactions
getTransactions 8 params → 200400401403404429500
GET
/transactions/{transactionId}
Get transaction by ID
getTransaction 1 param → 200400401403404429500
POST
/transactions/stake
Create a stake request
createStake 2 params body → 201400401403404409429500
POST
/transactions/unstake
Create an unstake request
createUnstake 2 params body → 201400401403404409429500
POST
/transactions/collect
Create a collect request
collectStaking 2 params body → 201400401403404409429500
POST
/transactions/consolidate-stake
Create a consolidate stake request
createConsolidateStake 2 params body → 201400401403404409429500
GET
/delegation-addresses/{assetType}
List supported delegation addresses
getDelegationAddresses 3 params → 200400401403404429500

Schemas 39

The contract defines 39 schemas that model the data the API accepts and returns. The most detailed are AMLQuestionnaire (22 properties), TransactionDetails (16 properties), WithdrawalRequest (14 properties), CreateUnstakeRequest (7 properties). Each schema is shown below with its type and property counts.

CreateStakeDetails
object
1 property 1 required
ETHStakingParameters
object
UNDER DEVELOPMENT: ETH specific staking parameters
3 properties 1 required
TransactionStatus
string
A string describing the status of the given transaction INITIATING - This transaction is being created SUCCESS - This transaction has succeeded NEEDSAPPROVAL -…
ResourceType
string
The type of the resource being referenced. Note that the VAULT type has been deprecated and WALLET should be used instead.
TransactionDetails
object
16 properties 8 required
WithdrawalParametersForXRP
object
Additional parameters to be provided exclusively when assetType is "XRP". When using a Trusted Destination, these parameters must not be provided — the destina…
1 property 1 required
TransactionType
string
The type of transaction "DEPOSIT" - A deposit has been detected in an Anchorage Digital vault "WITHDRAW" - A withdraw of funds from your Anchorage Digital vaul…
WithdrawalParametersForATOM
object
Additional parameters to be provided exclusively when assetType is "ATOM". This field is deprecated, please migrate to using assetParametersCosmos instead. Whe…
1 property 1 required
CreateCollectRequest
object
7 properties 3 required
SimpleSourceResourceDetails
object
An object representing a resource capable of sending funds. Construction example: { "id":"1c920f4241b78a1d483a29f3c24b6c4c", "type":"WALLET" }
2 properties 2 required
ResourceDetails
object
An object representing a resource capable of receiving, or holding funds. Construction example: { "id":"1c920f4241b78a1d483a29f3c24b6c4c", "type":"WALLET" }
2 properties 2 required
CreateCollectResponse
object
1 property 1 required
DelegationAddressesResponse
object
2 properties 2 required
ErrorDetails
object
2 properties 2 required
WithdrawalDetails
object
1 property 1 required
CreateUnstakeResponse
object
1 property 1 required
CreateStakeResponse
object
1 property 1 required
StakingParameters
objectnull
Sets specific assets configuration parameters to perform staking
CreateUnstakeRequest
object
7 properties 3 required
FiatDetails
object
Banking details for fiat transactions
6 properties
WithdrawalResponse
object
1 property 1 required
Page
object
Pagination info
1 property
CreateConsolidateStakeRequest
object
6 properties 5 required
WithdrawalParametersForFiatTrustedDestination
object
Additional parameters to be provided exclusively when the destination is a Trusted Destination and assetType is fiat.
2 properties 1 required
WithdrawalParametersForXLM
object
Additional parameters to be provided exclusively when assetType is "XLM". When using a Trusted Destination, these parameters must not be provided — the memo is…
1 property 1 required
CreateStakeRequest
object
6 properties 4 required
AMLQuestionnaire
object
Anti-money laundering questionnaire submission
22 properties 1 required
TransactionResponse
object
1 property 1 required
SOLStakingParameters
object
UNDER DEVELOPMENT: Solana specific staking parameters
2 properties
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
SimpleSourceResourceType
string
The type of the resource being referenced.
SourceResourceTypeRequest
string
The type of the resource being referenced. Note that the VAULT type has been deprecated and WALLET should be used instead.
WithdrawalParametersExtra
object
Extra parameters, to be provided for assets. When using a Trusted Destination, these parameters must not be provided — the memo is inherited from the trusted d…
1 property 1 required
WithdrawalParametersForCosmos
object
Additional parameters to be provided exclusively when assetType is for a Cosmos blockchain. When using a Trusted Destination, these parameters must not be prov…
1 property 1 required
ErrorType
string
The type of error returned.
WithdrawalRequest
object
14 properties 2 required
SourceResourceDetailsRequest
object
An object representing a resource capable of sending funds. Construction example: { "id":"1c920f4241b78a1d483a29f3c24b6c4c", "type":"WALLET" }
3 properties 2 required
TransactionsResponse
object
2 properties 2 required
DelegationWalletAddressesDetails
object
4 properties 4 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

anchorage-transactions-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
#Transaction
← Back to A APIs
API Details
ID
anchorage:anchorage-transactions-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-transactions-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/anchorage-transactions-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 Transactions 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.