Update transaction suspicious activities 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.
suspicious_activity_id
Unique identifier for a suspicious activity belonging to a transaction. This is the primary key for a transaction suspicious activity and should be unique across all transaction suspicious activities. Updates to a transaction suspicious activity should be made using this identifier.
timestamp
The time of the transaction suspicious activity. This should be in ISO 8601 format. When adding a new transaction suspicious activity, this field represents the detection time. When updating a transaction suspicious activity, this represents the time of the update.
detection_date
Timestamp at which suspicious activity was detected on a transaction. This should be in the ISO 8601 format.
report_id
Unique identifier for a transaction suspicious activity report for which the suspicious activity belongs to.
report_filed_at
The time of the transaction suspicious activity report was filed. This should be in ISO 8601 format.
Response
Transaction suspicious activity 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.