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

Anchorage Digital Transfers API

These endpoints allow you to transfer assets from one of your API-enabled vaults to *another resource custodied by Anchorage Digital*.

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

This API exposes 4 operations across 2 paths, and defines 22 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.

4 operations 2 paths 22 schemas 1 DELETE2 GET1 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
Resource Areas
1

Authentication & Security 1

Anchorage Digital Transfers 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 4

Across 2 paths, the API surfaces 4 operations — 1 DELETE, 2 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Transfers 4

These endpoints allow you to transfer assets from one of your API-enabled vaults to another resource custodied by Anchorage Digital.

GET
/transfers
List transfers
getTransfers 8 params → 200400401403404429500
POST
/transfers
Create a transfer request
createTransfer 3 params body → 201400401403404429500
GET
/transfers/{transferId}
Get transfer by ID
getTransfer 1 param → 200400401403404429500
DELETE
/transfers/{transferId}
Cancel a transfer request
cancelTransfer 3 params → 204400401403404409429500

Schemas 22

The contract defines 22 schemas that model the data the API accepts and returns. The most detailed are TransferAMLQuestionnaire (21 properties), TransfersRequest (15 properties), TransferDetails (12 properties), Amount (4 properties). Each schema is shown below with its type and property counts.

ResourceType
string
The type of the resource being referenced. Note that the VAULT type has been deprecated and WALLET should be used instead.
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
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
ResourceDetails
object
An object representing a resource capable of receiving, or holding funds. Construction example: { "id":"1c920f4241b78a1d483a29f3c24b6c4c", "type":"WALLET" }
2 properties 2 required
TransfersResponse2
object
1 property 1 required
ErrorDetails
object
2 properties 2 required
TransfersResponse1
object
1 property 1 required
TransferDetails
object
12 properties 5 required
TransfersResponse
object
2 properties 2 required
Page
object
Pagination info
1 property
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
Data3
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
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
SourceResourceType
string
The type of the resource being referenced. Note that the VAULT type has been deprecated and WALLET should be used instead.
TransfersRequest
object
15 properties 2 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
SourceResourceDetails
object
An object representing a resource capable of sending funds. Construction example: { "id":"1c920f4241b78a1d483a29f3c24b6c4c", "type":"WALLET" }
2 properties 2 required
ErrorType
string
The type of error returned.
TransferStatus
string
A string describing the status of the given transfer INPROGRESS - This transfer is in progress and is not final. COMPLETED - This transfer has been completed a…
TransferAMLQuestionnaire
object
Anti-money laundering questionnaire submission
21 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

anchorage-transfers-api-openapi.yml Raw ↑

Other APIs Anchorage Digital publishes across the network.

Anchorage Digital Addresses API
Anchorage Digital AML API
Anchorage Digital API Key API
Anchorage Digital Asset Types API
Anchorage Digital Asset Types & Networks API
Anchorage Digital Atlas Settlement Network API
Anchorage Digital Balances API
Anchorage Digital Collateral Management API
Anchorage Digital Deposit Attribution API
Anchorage Digital Fiat Banking Operations API
Anchorage Digital Onboarding API
Anchorage Digital Stablecoins API
Where this information came from

This is an independent, third-party profile of Anchorage Digital Transfers 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.