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

These endpoints allow creating, applying, removing, and searching tags on operations.

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

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

5 operations 4 paths 14 schemas 1 DELETE2 GET2 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 Tagging 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 5

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

Tagging 5

These endpoints allow creating, applying, removing, and searching tags on operations.

GET
/tags
List tags
listTags 2 params → 200400401403429500
POST
/tags
Create a tag
createTag body → 201400401403409429500
POST
/tags/apply
Apply tags to an entity
applyTags body → 200400401403429500
DELETE
/tags/apply/{entityId}/{tagName}
Remove a tag from an entity
deleteAppliedTag 2 params → 200400401403404429500
GET
/tags/search
Search entities by tag
searchTags 5 params → 200400401403429500

Schemas 14

The contract defines 14 schemas that model the data the API accepts and returns. The most detailed are ApplyTagsRequest (4 properties), TaggingResult (4 properties), CreateTagResponse (3 properties), TaggingPagination (3 properties). Each schema is shown below with its type and property counts.

ListTagsResponse
object
1 property 1 required
EntityTagsData
object
1 property 1 required
Tag
object
2 properties 2 required
ApplyTagsRequest
object
4 properties 4 required
TaggingPagination
object
3 properties 2 required
TaggingResult
object
4 properties 4 required
ErrorType
string
The type of error returned.
ApplyTagsResponse
object
1 property
CreateTagRequest
object
2 properties 2 required
SearchTagsResponse
object
2 properties 2 required
TagType
string
The ownership type of a tag.
ErrorDetails
object
2 properties 2 required
CreateTagResponse
object
3 properties 3 required
DeleteAppliedTagResponse
object
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

anchorage-tagging-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 Tagging 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.