Skip to main content
Settlements can also be viewed and monitored in the KeyStone Dashboard. Use the SDK for programmatic creation and automation.

create

Direct settlement creation when both parties are known by a single platform.
Direct creation vs. bilateral instructions: Use settlements.create() when your platform knows both parties upfront (single-platform use case). For cross-platform settlements - or when counterparties submit independently - use instructions.submit(). The bilateral instruction flow is the recommended approach for most integrations.

Parameters

SettlementPartyInput

SettlementLegInput


get

Fetch a settlement by ID with parties and legs.

SettlementRead

SettlementState

INSTRUCTED, COMPLIANCE_CHECKING, COMPLIANCE_CLEARED, AWAITING_DEPOSITS, SETTLED, FINALIZED, REJECTED, ROLLED_BACK, TIMED_OUT, MANUAL_REVIEW

list

Paginated list with optional state filter.

listEvents

State transition history for a settlement.

SettlementEventRead


submitComplianceDecision

Approve or reject a settlement flagged during compliance screening.
Only applicable when the settlement is in COMPLIANCE_CHECKING state with a flagged party.

getRelated

Get the opening and closing legs of a repo settlement pair.
Returns { opening: SettlementRead | null, closing: SettlementRead | null }.