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
Digital Asset

Digital Asset Registry API

The registry API from Digital Asset — 18 operation(s) for registry.

Documentation Provider Profile APIs.io OpenAPI GitHub

Digital Asset Registry API is one of 4 APIs that Digital Asset publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Registry. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 18 operations across 18 paths, and defines 17 schemas. It is described by OpenAPI 3.2.0, at version 2.1.0.

Requests are made against 4 base URLs: https://api.utilities.digitalasset.com, https://api.utilities.digitalasset-staging.com, https://api.utilities.digitalasset-dev.com, http://localhost:8080.

18 operations 18 paths 17 schemas 18 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.1.0
Base URL
https://api.utilities.digitalasset.com
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Digital Asset Registry API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (BearerAuth).

Paths & Operations 18

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

registry 18
POST
/api/utilities/v0/registry/mint/v0/offer
Get the factory and choice context for creating a mint offer.
getMintOfferCreateContext body → 200400404500
POST
/api/utilities/v0/registry/mint/v0/request
Get the factory and choice context for creating a mint request.
getMintRequestCreateContext body → 200400404500
POST
/api/utilities/v0/registry/burn/v0/offer
Get the factory and choice context for creating a burn offer.
getBurnOfferCreateContext body → 200400404500
POST
/api/utilities/v0/registry/burn/v0/request
Get the factory and choice context for creating a burn request.
getBurnRequestCreateContext body → 200400404500
POST
/api/utilities/v0/registry/mint/v0/offer/{mintOfferId}/choice-contexts/accept
Get the choice context to accept and execute a mint offer.
getMintOfferAcceptContext 1 param → 200400404500
POST
/api/utilities/v0/registry/mint/v0/offer/{mintOfferId}/choice-contexts/reject
Get the choice context to reject a mint offer.
getMintOfferRejectContext 1 param → 200400404500
POST
/api/utilities/v0/registry/mint/v0/offer/{mintOfferId}/choice-contexts/cancel
Get the choice context to cancel a mint offer.
getMintOfferCancelContext 1 param → 200400404500
POST
/api/utilities/v0/registry/mint/v0/request/{mintRequestId}/choice-contexts/accept
Get the choice context to accept and execute a mint request.
getMintRequestAcceptContext 1 param → 200400404500
POST
/api/utilities/v0/registry/mint/v0/request/{mintRequestId}/choice-contexts/reject
Get the choice context to reject a mint request.
getMintRequestRejectContext 1 param → 200400404500
POST
/api/utilities/v0/registry/mint/v0/request/{mintRequestId}/choice-contexts/cancel
Get the choice context to cancel a mint request.
getMintRequestCancelContext 1 param → 200400404500
POST
/api/utilities/v0/registry/burn/v0/offer/{burnOfferId}/choice-contexts/accept
Get the choice context to accept and execute a burn offer.
getBurnOfferAcceptContext 1 param → 200400404500
POST
/api/utilities/v0/registry/burn/v0/offer/{burnOfferId}/choice-contexts/reject
Get the choice context to reject a burn offer.
getBurnOfferRejectContext 1 param → 200400404500
POST
/api/utilities/v0/registry/burn/v0/offer/{burnOfferId}/choice-contexts/cancel
Get the choice context to cancel a burn offer.
getBurnOfferCancelContext 1 param → 200400404500
POST
/api/utilities/v0/registry/burn/v0/request/{burnRequestId}/choice-contexts/accept
Get the choice context to accept and execute a burn request.
getBurnRequestAcceptContext 1 param → 200400404500
POST
/api/utilities/v0/registry/burn/v0/request/{burnRequestId}/choice-contexts/reject
Get the choice context to reject a burn request.
getBurnRequestRejectContext 1 param → 200400404500
POST
/api/utilities/v0/registry/burn/v0/request/{burnRequestId}/choice-contexts/cancel
Get the choice context to cancel a burn request.
getBurnRequestCancelContext 1 param → 200400404500
POST
/api/utilities/v0/registry/burn-mint-instruction/v0/burn-mint-factory
Get the burn mint factory and choice context for burn and mint.
getBurnMintFactory body → 200400404500
POST
/api/utilities/v0/registry/transfer/v0/proof
Verify the outcome of a transfer of Registry Utility assets on Canton. Given an UpdateID and a Transfer Object, the service looks up the corresponding ledger transaction and verifies the transfer det…
verifyTransferProof body → 200400500

Schemas 17

The contract defines 17 schemas that model the data the API accepts and returns. The most detailed are TransferObject (8 properties), ContractMeta (5 properties), RequestBurnRequest (3 properties), GetBurnMintFactoryRequest (3 properties). Each schema is shown below with its type and property counts.

TransferMeta
object
Additional metadata associated with the transfer.
1 property 1 required
FactoryWithChoiceContext
object
A factory contract together with the choice context required to exercise the choice provided by the factory. Typically used to implement the generic initiation…
2 properties 2 required
VerifyTransferProofResponse
object
The outcome of verifying a transfer proof.
1 property 1 required
RequestBurnRequest
object
The request to get the factory and choice context for creating a burn request.
3 properties 3 required
RequestMintRequest
object
The request to get the factory and choice context for creating a mint request.
2 properties 2 required
ChoiceContext
object
The context required to exercise a choice on a contract via an interface. Used to retrieve additional reference date that is passed in via disclosed contracts,…
2 properties 2 required
GetBurnMintFactoryRequest
object
The request to get the factory and choice context for burn and mint.
3 properties 3 required
TransferObject
object
The transfer payload containing transaction details known only to the sender and receiver.
8 properties 8 required
OfferBurnRequest
object
The request to get the factory and choice context for creating a burn offer.
2 properties 2 required
OfferMintRequest
object
The request to get the factory and choice context for creating a mint offer.
2 properties 2 required
MintOutput
object
The output to be minted.
2 properties 2 required
VerifyTransferProofRequest
object
Request to verify the outcome of a transfer of Registry Utility assets on Canton.
2 properties 2 required
InstrumentId
object
The identifier of the instrument.
2 properties 2 required
TransferProofStatus
string
The status of the transfer proof verification: - Success: The proof is verified and the transfer was successfully concluded - Failure: The proof is verified, b…
ContractMeta
object
5 properties 2 required
DisclosedContract
Error
object
A problem occurred with processing the request. For instance: syntactically invalid JSON body, missing required fields, etc.
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

digital-asset-registry-api-openapi.yml Raw ↑

Other APIs Digital Asset publishes across the network.

Digital Asset Common API
AE Profile APIs.io
Digital Asset Operator API
AE Profile APIs.io
Digital Asset Public API
AE Profile APIs.io
#Registry
← Back to D APIs
API Details
ID
digital-asset:digital-asset-registry-api
Base URL
https://api.utilities.digitalasset.com
Docs
https://docs.digitalasset.com/registry/apis/operator-backend-api
Provider
Digital Asset
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=digital-asset-registry-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/digital-asset-registry-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 Digital Asset Registry 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.