Classify activities
Classify one or more activities by applying tags and optionally sending feedback to the originating provider.
Tags are applied to every activity specified in activityIds. All tag and activity validations are
atomic — if any ID is invalid or inaccessible, the entire request fails with no partial application.
Tag constraints:
- Tags must have domain
ACTIVITY; any other domain results in error. - Tags must not mix
FALSE_POSITIVEcategory with other categories. - Tags are re-applied if the activity was previously classified (idempotent update).
Authorizations
Headers
Your API key provided by FrankieOne
"245c765b124a098d09ef8765...."
Your Customer ID provided by FrankieOne
"12345678-1234-1234-1234-123456789012"
Your Customer Child ID provided by FrankieOne
"87654321-4321-4321-4321-210987654321"
Open string that can be used to define the "channel" the request comes in from. It can potentially be used in routing and risk calculations upon request. Default values that can be used are: api portal smartui Any alphanumeric string is supported though. Anything over 64 characters will be truncated.
Username provided by API caller
"fred.flintstone@frankieone.com"
Body
Request to classify one or more activities with tags and optionally provide feedback to the originating provider.
The entity that owns the activities being classified.
"3fa85f64-5717-4562-b3fc-2c963f66afa6"
IDs of the activities to classify. All activity IDs must exist and belong to the specified entity. If any are invalid or belong to a different tenant the entire request fails with 404 (to prevent data existence leakage).
1[
"01HN9XHZN6MGXM9JXG50K59Q85",
"01HN9XHZN6MGXM9JXG50K59Q86"
]IDs of tags to apply as classifications to the specified activities. Retrieve available tag IDs
via GET /v2/tags (Core V2 API), filtering by relevant categories and domain
(e.g. ?categories=FRAUD,MONEY_LAUNDERING,SCAM,TERRORISM_FINANCING,PROLIFERATION_FINANCING&domains=ACTIVITY).
All tags must exist and be accessible to the customer (SYSTEM or owned CUSTOMER tags). Duplicate IDs are silently removed.
Ordering: The first tag in the array is treated as the primary reason when sending feedback to providers that support only a single classification.
Validation rules:
Tags with category FALSE_POSITIVE must not be mixed with tags from other categories
(e.g. FRAUD, SCAM) — the intent cannot be reconciled and the request will be rejected with 422.
Tags with category IN_REVIEW follow the same mutual-exclusivity rule — IN_REVIEW tags do not
trigger provider feedback and must not be combined with non-IN_REVIEW tags.
1[
"12345678-1234-1234-1234-123456789012",
"87654321-4321-4321-4321-210987654321"
]Optional comment to be recorded in the audit log for this classification.