ledger.submitAndWaitForReassignment

submitAndWaitForReassignment posts POST /v2/commands/submit-and-wait-for-reassignment. Supply reassignmentCommands describing commandId, submitter, and individual commands array entries compatible with ReassignmentCommand payloads.

Receiver: await canton.ledger.submitAndWaitForReassignment

Setup

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

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

Minimal example

const result = await canton.ledger.submitAndWaitForReassignment({
  reassignmentCommands: {
    commandId: 'reassign-001',
    submitter: canton.getPartyId(),
    commands: [],
  },
});

Parameters — `SubmitAndWaitForReassignmentParams`

reassignmentCommands (required) — Includes commandId, submitter, commands, optional workflowId, userId, submissionId per BaseReassignmentCommand validation.
eventFormat (optional) — OperationEventFormat customizing reassignment event payloads (filtersByParty, optional filtersForAnyParty, verbose).

Returns — `JsSubmitAndWaitForReassignmentResponse`

Structured reassignment output from the participant (SDK schema JsSubmitAndWaitForReassignmentResponse).

Errors and pitfalls

Invalid topology state or authorization failures reject like command submits.

Auth and party

OAuth token; submitter must be authorized for the reassignment action.

Source

operations/v2/commands/submit-and-wait-for-reassignment.ts