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

Anti-Money Laundering compliance endpoints

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

This API exposes 1 operation across 1 path, and defines 19 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.

1 operations 1 paths 19 schemas 1 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 AML 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 1

Across 1 path, the API surfaces 1 operation — 1 POST. Each is listed below with its method, path, parameters, and response codes.

AML 1

Anti-Money Laundering compliance endpoints

POST
/aml/submit-info
Submit AML information
submitAMLInfo body → 200400401403429500

Schemas 19

The contract defines 19 schemas that model the data the API accepts and returns. The most detailed are AMLOriginator (9 properties), AMLSubmitInfoRequest (8 properties), AMLBeneficiaryIndividualInfo (8 properties), AMLBeneficiaryEntityInfo (8 properties). Each schema is shown below with its type and property counts.

AMLOriginatorExtraInfo
object
Additional optional information about the originator.
2 properties
AMLBeneficiaryIndividualInfo
object
Beneficiary information when the beneficiary is a natural person.
8 properties 3 required
ErrorDetails
object
1 property 1 required
AMLOriginatorType
string
Type of originator.
AMLSubmitInfoRequest
object
8 properties 6 required
AMLSubmitInfoResponse
object
1 property 1 required
AMLBeneficiaryEntityInfo
object
Beneficiary information when the beneficiary is an entity.
8 properties 3 required
AMLDestination
object
The Virtual Asset Service Provider (VASP) or self-hosted wallet receiving the funds.
3 properties 1 required
AMLPurpose
string
The purpose of the transaction.
AMLDestinationType
string
Type of destination.
AMLBeneficiaryDestinationInfo
object
Beneficiary information when the beneficiary is the destination VASP itself.
2 properties 2 required
AMLStructuredSubmission
object
Structured AML submission data. Required fields are enforced by the server based on the intent.
4 properties
AMLWalletOwnerType
string
Indicates who owns the self-hosted wallet.
AMLSelfHostedInfo
object
Information about a self-hosted wallet destination.
2 properties 1 required
AMLOriginator
object
The organization or client initiating the transaction.
9 properties 4 required
AMLCustodialInfo
object
Information about a custodial VASP destination.
2 properties 2 required
AMLTxIntent
string
The intent of the transaction.
AMLBeneficiaryType
string
Type of beneficiary.
AMLBeneficiary
object
The recipient of the transaction.
4 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

anchorage-aml-api-openapi.yml Raw ↑

Other APIs Anchorage Digital publishes across the network.

Anchorage Digital Addresses 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
Anchorage Digital Statements API
Where this information came from

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