Update screenings in batch
Headers
Authorization
Bearer authentication of the form Bearer <token>, where token is your auth token.
Authorization
Request
This endpoint expects a list of objects.
screening_id
Unique identifier for the screening. This is the primary key for a screening and should be unique across screenings.
outcome
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.
timestamp
The time of the screening. This should be in ISO 8601 format and represents the creation or update time of the screening.
type
The type of screening check performed (e.g., SANCTION, PEP, ADVERSE_MEDIA, etc.).
Allowed values:
outcome_details
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.
provider
The provider that performed the screening check.
lists
The list(s) that the transaction was screened against. E.g. OFAC, ComplyAdvantage, Watchlists…
Response
Screening updated successfully
success
Indicates if the write operation was successful.
write_count
The number of records written to the database.
message
Provides additional information about the operation result.
organization_id
The organization ID for which the operation was performed.