Skip to main content
POST
Trigger Monitoring

Endpoint

Overview

Manually trigger the screening process for a specific watchlist. This executes the ongoing monitoring check immediately instead of waiting for the next scheduled check, returning the results synchronously.
This is useful for:
  • Immediate screening after adding new subjects
  • On-demand compliance checks
  • Testing watchlist configuration before going live

Authentication

Requires watchlist:update permission.

Path Parameters

string
required
The unique identifier of the watchlist to monitor

Request Example

Response

Success Response (200 OK)

Response Fields

Error Responses

400 Bad Request - Watchlist Not Active

The watchlist is paused. Update the status to active first.

400 Bad Request - No Subjects

The watchlist has no subjects. Add subjects before triggering monitoring.

404 Not Found

Usage Examples

Python

JavaScript

Status Codes

Best Practices

For watchlists with check_frequency: "on_update", use this endpoint to trigger manual checks whenever needed instead of relying on scheduled checks.
When adding subjects to an active watchlist, consider triggering an immediate check to get screening results without waiting for the next scheduled run.
The has_changes field indicates whether any subjects gained or lost matches since the last check. Use this to trigger downstream processes only when needed.
The breakdown by list helps identify which sanctions lists are triggering matches, useful for risk assessment and compliance reporting.

Rate Limiting

Monitoring operations are resource-intensive. Avoid triggering monitoring too frequently:
  • For daily watchlists, limit to 1-2 manual triggers per day
  • For large watchlists (100+ subjects), allow 5-10 minutes between triggers

Next Steps