Token Standard off-ledger API

In order to interact with the Registry App over CIP-56, certain contract disclosures need to be sourced via an off-ledger API. These endpoints are specific to each instrument admin, and are exposed with the following base URL:

MainNet
TestNet
DevNet

https://api.utilities.digitalasset.com/api/token-standard/v0/registrars/<admin-party-id>

https://api.utilities.digitalasset-staging.com/api/token-standard/v0/registrars/<admin-party-id>

https://api.utilities.digitalasset-dev.com/api/token-standard/v0/registrars/<admin-party-id>

where <admin-party-id> is the party identifier of the target instrument admin.

Example: USDCx instrument metadata

The instrument admin for USDCx is the party decentralized-usdc-interchain-rep::12208115f1e168dd7e792320be9c4ca720c751a02a3053c7606e1c1cd3dad9bf60ef.Hence, the instrument metadata endpoint for USDCx on MainNet can be retrieved using the following URLhttps://api.utilities.digitalasset.com/api/token-standard/v0/registrars/decentralized-usdc-interchain-rep::12208115f1e168dd7e792320be9c4ca720c751a02a3053c7606e1c1cd3dad9bf60ef/registry/metadata/v1/instruments/USDCx.

Instrument admin discovery

There is currently no standardized way to discover the set of instrument admins, and their respective instruments.

Token Standard API (CIP 56)Get apitoken standardv0registrars registrymetadatav1info

⌘I

​Instrument admin discovery

Instrument admin discovery