Configure a ComplyAdvantage Mesh webhook to receive alerts when a monitored case gets new sanctions/PEP hits
domain: docs.mesh.complyadvantage.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Create a webhook configuration against the notification/webhook endpoint, specifying your callback URL
Subscribe to CASE_ALERT_LIST_UPDATED to be notified when an ongoing monitored case surfaces new alert hits
Optionally also subscribe to CASE_TRANSITIONED and CUSTOMER_RISK_LEVEL_INCREASED/DECREASED to track case status and risk-level changes
On receiving CASE_ALERT_LIST_UPDATED, fetch the case's current alert list via the API rather than trusting the webhook payload as the full state
Route newly surfaced alerts into your manual review queue rather than auto-resolving them
Known gotchas
These event names belong to the current Mesh platform docs — older ComplyAdvantage 'classic' API integrations use different terminology and won't match if you mix documentation versions
CASE_ALERT_LIST_UPDATED signals that the alert list changed, not what specifically changed, so you still need to re-fetch the case to see the new hit
Ongoing monitoring only fires these events for cases explicitly placed under monitoring — a one-time search that was never attached to a monitored case will never trigger this webhook
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?