Skip to content
← Open Cap Table Protocol Canton Node SDK

Reference

lookupAnsEntryByParty

GET scan-proxy ANS lookup keyed by supplying ledger party identifiers embedded URL-encoded path segments.

lookupAnsEntryByParty resolves catalogue listings tying Canton participation proofs (Alice::1220…) back toward UX-ready descriptors.

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.lookupAnsEntryByParty.

Minimal example

const entry = await canton.validator.lookupAnsEntryByParty({
  party: 'Alice::1220abcdef...',
});

Parameters

  • party (required, string) — Fully-qualified Canton Party identifier routed verbatim (encodeURIComponent applied internally).

Returns

Scan-proxy JSON for the given party’s ANS entry.

Errors and pitfalls

  • Parties lacking catalogue registrations yield absence semantics mirrored HTTP-wise via validator semantics—consult logs carefully versus UX assumptions.

Auth and party

Bearer authorization referencing authenticated wallets leveraging Validator APIs.

See also

Source

src/clients/validator-api/operations/v0/ans/lookup-by-party.ts on GitHub.