Skip to main content
POST
Add a User to Monitoring
Places one of your customers under ongoing AML monitoring by the given bot. The bot re-checks each enrolled subject on its configured cadence.
You usually don’t need this endpoint. Saving transactions auto-provisions and enrols a subject on first sight. Use this to enrol a customer who has no transactions yet, or to attach an existing customer to an additional bot.
Field names are documented in snake_case and responses always use snake_case; requests also accept camelCase. The call is idempotent. Re-adding a subject who is already enrolled returns 200 with the existing enrolment and does not reset its cadence or check schedule. Re-adding a subject who was previously removed reactivates them.

Request

Headers

Path parameters

Body parameters

Example request

Response

201 — Enrolled · 200 — Already enrolled

201 means the subject was newly enrolled. 200 means they were already enrolled and the existing enrolment is returned unchanged.

Error responses

Sandbox

With a sandbox API key this endpoint performs full validation — an unknown bot or subject still returns 404 — and returns a realistic enrolment, but stores nothing.

Coming next

Endpoints to list and remove monitored users, and to retrieve monitoring alerts, are in development.