getRegistryInfo

getRegistryInfo returns which registry-backed endpoints exist (supportedApis) for the validator-proxied token-standard deployment backing wallet tooling.

Setup

import { Canton } from '@fairmint/canton-node-sdk';

const canton = new Canton({
  network: 'devnet',
  provider: '5n',
  partyId: 'OWN_PARTY_ID',
});

Import and receiver

import { Canton } from '@fairmint/canton-node-sdk';

Receiver: canton.validator.getRegistryInfo.

Minimal example

const info = await canton.validator.getRegistryInfo();
console.log(info.adminId, info.supportedApis);

Parameters

None.

Returns

• adminId (string) — Instrument admin identifier advertised by registry.
• supportedApis (record string→number) — Capability bitmask keyed by splice REST surfaces exposed via scan-proxy.

Errors and pitfalls

• Rare infra outages propagate generic HTTP failures—retry once Canton infra dashboards indicate recovery.

Auth and party

Authenticated bearer token; descriptive discovery rarely restricts beyond OAuth gate.

See also

• listInstruments

Source

src/clients/validator-api/operations/v0/scan-proxy/registry/metadata/v1/get-registry-info.ts on GitHub.