API REFERENCE · SCHEMA
Counterparty
Required fields are always present in their containing object. Optional fields may be omitted; null is allowed only where stated. Array item fields apply to every item.
Counterparty history item when kind=cases.
idRequired- string
Format: uuid.
created_atRequired- string
Format: date-time.
decisionRequired- string
Values: "open", "confirmed", "dismissed".
business_dispositionRequired- string
Values: "pending", "allow", "restrict", "escalate".
review_stateRequired- string
screening_idRequired- string
Format: uuid.
latest_screening_idRequired- string or null
May be null.
latest_screening_id fields and rules
Allowed alternatives
- string
Format: uuid.
- null
May be null.
- string
Use CounterpartyCaseHistory in a workflow
Used by
Open an operation for its complete request or response example, including any outer JSON object that wraps these fields.
- GET /counterparties/{id}Response · Read a counterparty and linked screening, case and monitor history
- GET /counterparties/{id}/historyResponse · Page through linked history including truthful expired evidence metadata