Skip to main content

Configuration

The Configuration endpoints allow you to control the global behavior of the TruRisk AI module. These settings dictate which fields are enabled for screening, set the default processing mode, and manage ongoing monitoring alerts.

Prerequisites

Configuration changes apply globally to all future screening requests. It is recommended to perform this setup once during the initial integration.

default_mode determines which mode runs whenever a Customer or Compliance Request is submitted without an explicit tru_risk_mode. Setting TruRisk Lite as the default favors throughput and suits organizations screening high volumes of routine onboarding cases. Setting TruRisk Advanced as the default favors verification depth and documentation, and suits organizations whose case mix is weighted toward higher-risk or regulator-facing reviews. Either default can still be overridden on a per-request basis.

Get Configuration

Retrieves the current global settings for the TruRisk module.

Endpoint: https://api.amlwatcher.com/api/tru-risk-configuration

Method: GET

Request
GET /api/tru-risk-configuration HTTP/1.1
Host: api.amlwatcher.com
Authorization: Bearer Token

Response Body

ParameterTypeDescription
enabledBooleanMaster switch for the TruRisk module.
default_modeStringThe default operational mode (TruRisk Lite or TruRisk Advanced).
tru_risk_process_recordsIntegerThe limit of records processed per batch.
lite_inputsObjectConfiguration toggles for mandatory fields when using Lite mode.
advanced_fieldsObjectConfiguration toggles for optional high-fidelity fields in Advanced mode.
ongoing_monitoring_enabledBooleanIndicates if automated re-screening is active for the organization.
ongoing_monitoring_frequencyStringThe cadence of re-screening (e.g., Instantly).
alertsObjectContains settings for email_enabled, webhook_enabled, and email_recipients.
created_atStringTimestamp of the initial configuration setup.
updated_atStringTimestamp of the last configuration change.

Sample Response

Sample Response
{
"data": {
"configuration": {
"advanced_fields": {
"address": false,
"biometric_search_image": true,
"birth_incorporation_date": true,
"business_registration_number": false,
"identification_number": true,
"imo_number": false,
"industry": false,
"known_alias": false,
"name": true,
"nationality": true,
"occupation": false,
"parent": true,
"sibling": true,
"spouse": false,
"tail_number": false
},
"alerts": {
"email_enabled": true,
"email_recipients": "compliance@example.com, admin@example.com",
"webhook_enabled": true
},
"created_at": "Mon, 16 Feb 2026 10:33:49 GMT",
"default_mode": "TruRisk Advanced",
"enabled": true,
"lite_inputs": {
"biometric_search_image": true,
"birth_incorporation_date": true,
"countries": true,
"name": true
},
"ongoing_monitoring_enabled": true,
"ongoing_monitoring_frequency": "Instantly",
"tru_risk_process_records": 50,
"updated_at": "Mon, 16 Feb 2026 10:33:49 GMT"
}
},
"error": false,
"status": "SUCCESS"
}

lite_inputs and advanced_fields let each organization tailor which identity attributes are required or available for screening, based on the data it actually collects during onboarding. Enabling a field here makes it usable by TruRisk's identity resolution logic—it does not, on its own, make that field mandatory on every request unless the field is marked required.


Update Configuration

Updates the global AI behavior and field requirements.

Endpoint: https://api.amlwatcher.com/api/tru-risk-configuration

Method: POST

Request
POST /api/tru-risk-configuration HTTP/1.1
Host: api.amlwatcher.com
Content-Type: application/json
Authorization: Bearer Token

{
"enabled": true,
"default_mode": "TruRisk Advanced",
"tru_risk_process_records": 50,
"lite_inputs": {
"name": true,
"birth_incorporation_date": true,
"biometric_search_image": true,
"country": true
},
"advanced_fields": {
"name": true,
"birth_incorporation_date": true,
"biometric_search_image": true,
"nationality": true,
"identification_number": true,
"parent": true,
"sibling": true,
"occupation": true,
"industry": true,
"spouse": false,
"address": false,
"imo_number": true,
"tail_number": true,
"business_registration_number": true,
"known_alias": true
},
"ongoing_monitoring_enabled": true,
"ongoing_monitoring_frequency": "Monthly",
"alerts": {
"email_enabled": true,
"email_recipients": "compliance@example.com",
"webhook_enabled": true
}
}

Request Body

Required fields on every update

For POST /api/tru-risk-configuration, the following top-level fields must be sent together every time: enabled, default_mode, and tru_risk_process_records.

Inside nested objects, name is also required in both lite_inputs and advanced_fields.

ParameterTypeRequiredDescription
enabledBooleanYesMaster switch for TruRisk.
default_modeEnumYesMust be TruRisk Lite or TruRisk Advanced.
tru_risk_process_recordsIntegerYesNumber of records processed per batch.
lite_inputsObjectYesLite-mode field toggles.
lite_inputs.nameBooleanYesRequired switch for name in Lite mode.
advanced_fieldsObjectYesAdvanced-mode field toggles.
advanced_fields.nameBooleanYesRequired switch for name in Advanced mode.
ongoing_monitoring_enabledBooleanNoEnables or disables ongoing monitoring.
ongoing_monitoring_frequencyEnumNoMonitoring cadence (e.g., Instantly, Daily, Weekly, Monthly, Do not run).
alertsObjectNoAlert delivery preferences.
alerts.email_enabledBooleanNoToggle email alerts.
alerts.email_recipientsStringNoComma-separated emails for alert delivery.
alerts.webhook_enabledBooleanNoToggle webhook alerts.

Additional validation notes

  • default_mode is validated against purchased/enabled org capabilities.
  • advanced_fields must include at least one enabled advanced driver (or DOB) as enforced by API validation.
  • Unknown keys inside advanced_fields are rejected.

TruRisk's default calibration takes a balanced, industry-aligned approach that weighs both false positives and false negatives rather than optimizing for one at the expense of the other. Regardless of configuration, the accuracy of verdicts and confidence scoring remains dependent on the completeness and quality of the profile data submitted.

Response Body

ParameterTypeDescription
statusStringIndicates the result of the request (e.g., SUCCESS).
errorBooleanIndicates if the update failed.
data.messageStringA confirmation message (e.g., "TruRisk configuration saved successfully").
data.configuration.enabledBooleanConfirmation of the module's master switch status.
data.configuration.default_modeStringThe newly set default mode (TruRisk Lite or TruRisk Advanced).
data.configuration.tru_risk_process_recordsIntegerThe limit of records processed per batch.
data.configuration.lite_inputsObjectThe saved toggles for mandatory Lite mode fields.
data.configuration.advanced_fieldsObjectThe saved toggles for optional Advanced mode fields.
data.configuration.ongoing_monitoring_enabledBooleanConfirmation of automated re-screening status.
data.configuration.ongoing_monitoring_frequencyStringCadence of re-screening (e.g., Instantly).
data.configuration.alertsObjectSettings for email_enabled, webhook_enabled, and email_recipients.
data.configuration.updated_atStringTimestamp reflecting the exact moment the settings were saved.

Sample Response

Sample Response
{
"data": {
"configuration": {
"advanced_fields": {
"address": false,
"biometric_search_image": true,
"birth_incorporation_date": true,
"business_registration_number": false,
"identification_number": true,
"imo_number": false,
"industry": false,
"known_alias": false,
"name": true,
"nationality": true,
"occupation": false,
"parent": true,
"sibling": true,
"spouse": false,
"tail_number": false
},
"alerts": {
"email_enabled": true,
"email_recipients": "compliance@example.com",
"webhook_enabled": true
},
"created_at": "Mon, 16 Feb 2026 10:33:49 GMT",
"default_mode": "TruRisk Advanced",
"enabled": true,
"lite_inputs": {
"biometric_search_image": true,
"birth_incorporation_date": true,
"countries": true,
"name": true
},
"ongoing_monitoring_enabled": true,
"ongoing_monitoring_frequency": "Instantly",
"tru_risk_process_records": 50,
"updated_at": "Mon, 16 Feb 2026 10:33:49 GMT"
},
"message": "TruRisk configuration saved successfully"
},
"error": false,
"status": "SUCCESS"
}

How Ongoing Monitoring Works

When ongoing_monitoring_enabled is turned on, TruRisk automatically re-evaluates a monitored customer whenever a new screening match appears against that entity, new adverse media is detected, or the customer's profile data is updated. Each re-evaluation refreshes the case's risk score and verdict, and—based on the alerts settings above—sends a notification by email, webhook, or both, so compliance teams are notified of the change rather than needing to re-check cases manually. ongoing_monitoring_frequency controls how often this re-evaluation cycle runs.