🗑 Concealed data of a batch of transaction results.
This endpoint redacts multiple transactions, masking the user's personal data for privacy. It is irreversible.
Redact Multiple Transactions - Success
Below is a successful response to the redacted transaction:
{
"status": "success",
"transaction_ids": [
"transaction_id_1",
"transaction_id_2",
...
],
"redacted_at": "2022-05-25T05:02:17.979Z",
"redacted_data": [
"records",
"assets",
"face",
"data"
]
}
Redact Multiple Transactions - Error
When the request has invalid syntax, the server will generate the following error response:
{
"error_message": "Bad Request."
}
When an incorrect or expired access token is used, the following error response will appear:
{
"error_message": "Unauthenticated."
}
If any of the transactionId
is invalid, you will get the following error response:
{
"error_message": "The token was not found."
}
If any of the transactions are in progress and not yet ready for redaction, the following error response will appear:
{
"error_message": "Transaction not ready for redaction."
}
The following error response will appear when the server encounters a situation it doesn't know how to handle:
{
"error_message": "Internal Server Error."
}
For the details of the payload response, please refer to the table below:
Fields | Data Type | Mandatory/Optional | Description |
---|---|---|---|
status | string | Mandatory | The redaction result status. There are two possible responses, i.e., success or error . |
transaction_ids | array | Mandatory | The transaction ID array that is going to be redacted. If an error occurs, an empty array will be returned. |
redacted_at | timestamp | Mandatory | The timestamp when the record was redacted. It returns null if an error occurs. |
redacted_data | array | Mandatory | An array of redacted data, i.e., records , assets , face , and data . |
error_message | string | Optional | The error message, depicting what the error actually is, for example, "Transaction not ready for redaction." |
💬 We Are Here to Help!
If you encounter an issue, a bug, or require assistance, please contact our support page here to find the solution. Don't forget to provide any important information on the issue.