v1
latestOpenAPI 3.0.32026-08-04404186.8 KBUpdate screenings in batch
Request body
The list(s) that the transaction was screened against. E.g. OFAC, ComplyAdvantage, Watchlists...
The outcome of the screening check (e.g., POSITIVE, NEGATIVE, TRUE_POSITIVE, etc.). The value "SCREENED" should only be used when the outcome is not available but there is the confirmation that the screening has been done.
Further details on the reason of the screening outcome. For a transaction screening, it could be due to many reasons, so it could be relevant to include further details.
The provider that performed the screening check.
Unique identifier for the related company in case of a company screening. Only one of related_tx_id, related_person_id or related_company_id should be provided.
Unique identifier for the related person in case of a person and/or transaction screening. Only one of related_tx_id, related_person_id or related_company_id should be provided.
Unique identifier for the related transaction in case of a transaction screening. Only one of related_tx_id, related_person_id or related_company_id should be provided.
Unique identifier for the screening. This is the primary key for a screening and should be unique across screenings.
When the screening was performed in your system, in ISO 8601 format.
The type of screening check performed (e.g., SANCTION, PEP, ADVERSE_MEDIA, etc.).
Response
Screening updated successfully
Provides additional information about the operation result.
The organization ID for which the operation was performed.
Indicates if the write operation was successful.
The number of records written to the database.