| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
Overview
Use this method to remove tags from a particular transaction. You can remove both custom tags added by operators or via API ("type": "userDefined") and tags added automatically by transaction monitoring rules ("type": "system").
To check which tags a transaction has and their exact labels, use Get transaction tags.
Notes
Tag names (labels) are case sensitive. For example,
Suspiciousandsuspiciousare considered different.Tags that do not exist on the transaction are ignored and return no error.
Removing tags from a transaction does not remove them from the Dashboard settings.
Required permissions
To use this method, your app token must have the Manage TM transactions - Review permission.
Request example
curl -X DELETE \
'https://api.sumsub.com/resources/kyt/txns/66c46d7566f5244e45a00000/tags' \
-H 'content-type: application/json' \
-H 'X-App-Token: <your-app-token>' \
-H 'X-App-Access-Sig: <your-signature>' \
-H 'X-App-Access-Ts: <unix-timestamp>' \
-d '[
"Anomaly med",
"Suspicious pattern"
]'Response explained
If the request is sent and processed correctly, you may receive one of the following responses:
- When the transaction still holds tags, you will get the JSON file containing an array of objects representing the remaining tags. For example:
[
{
"label": "Bonus abuse",
"type": "userDefined"
},
{
"label": "Suspicious pattern",
"type": "userDefined"
}
]- When all tags are removed, the response will return no content.
No ContentIf the request fails, you will receive an HTTP response containing an error code along with a message explaining the error.
For example:
{
"description": "The request body must not be null",
"code": 400,
"correlationId": "9fb77d5080ca4efd4ab19624e50a1baf"
}No error is returned in cases where you specify non-existing tags in your request.