Anchorage Digital Onboarding API
These endpoints allow clients/partner institutions to start the customer onboarding process for a B2B2B/B2B2C end customer who would not be using the Anchorage Digital applications directly. They collect the required data and documentation for Anchorage Digital to satisfy its regulatory obligations to perform KYB/KYC, CIP, CDD and EDD on its customers and related parties.Currently only B2B2B/B2B2C customer onboarding is supported.### Payload DataThe "customer" endpoints take a payload of `entries` in an array of key/value pairs. Details on the required and support key/value pairs is available in documentation provided by Anchorage Digital. Please contact your Customer Experience representative for details.Note that some of the keys are conditional depending on the presence or value of other key/value pairs. For example, the key `legalStructureOther` is only required if the `legalStructure` key has the Enum value `OTHER`.Also note that every `value` field accepts primitives, objects and collections, which makes the payload very flexible for the client's needs.For example, both of the following `entries` are accepted and interchangeable:```json{ "entries":[ { "key":"boolField", "value":true }, { "key":"numberField", "value":10 }, { "key":"stringField", "value":"stringFieldValue" }, { "key":"collectionField", "value":[ "collectionField0Value", "collectionField1Value" ] }, { "key":"objectField", "value":{ "field0":"field0Value", "field1":"field1Value", "field2":"field2Value" } }, { "key":"objectCollectionField", "value":[ { "field0":"field0AValue", "field1":"field1AValue", "field2":"field2AValue" }, { "field0":"field0BValue", "field1":"field1BValue", "field2":"field2BValue" } ] } ]}``````json{ "entries":[ { "key":"boolField", "value":true }, { "key":"numberField", "value":10 }, { "key":"stringField", "value":"stringFieldValue" }, { "key":"collectionField.0", "value":"collectionField0Value" }, { "key":"collectionField.1", "value":"collectionField1Value" }, { "key":"objectField.field0", "value":"field0Value" }, { "key":"objectField.field1", "value":"field1Value" }, { "key":"objectField.field2", "value":"field2Value" }, { "key":"objectCollectionField.0.field0", "value":"field0AValue" }, { "key":"objectCollectionField.0.field1", "value":"field1AValue" }, { "key":"objectCollectionField.0.field2", "value":"field2AValue" }, { "key":"objectCollectionField.1.field0", "value":"field0BValue" }, { "key":"objectCollectionField.1.field1", "value":"field1BValue" }, { "key":"objectCollectionField.1.field2", "value":"field2BValue" } ]}```
Anchorage Digital Onboarding 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 Onboarding. The published artifact set on APIs.io includes an OpenAPI specification.
This API exposes 14 operations across 9 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.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 1
Anchorage Digital Onboarding 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 14
Across 9 paths, the API surfaces 14 operations — 6 GET, 6 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.
These endpoints allow clients/partner institutions to start the customer onboarding process for a B2B2B/B2B2C end customer who would not be using the Anchorage Digital application…
Schemas 34
The contract defines 34 schemas that model the data the API accepts and returns. The most detailed are CreateKYCAgreementResponseData (8 properties), GetKYCAgreementResponseData (8 properties), CreateKYCAgreementRequest (7 properties), KYCSubaccountApplication (6 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Anchorage Digital 12
Other APIs Anchorage Digital publishes across the network.
This is an independent, third-party profile of Anchorage Digital Onboarding 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.