Enable or disable monitoring by entity and integration
API Reference
Enable or disable monitoring by entity and integration
PATCH /entities/toggle-status-monitoring — provider-code–extensible — in the gu1 entity monitoring service for ongoing screening, with examples for patch.
PATCH
Enable or disable monitoring by entity and integration
Documentation Index
Fetch the complete documentation index at: https://docs.gu1.ai/llms.txt
Use this file to discover all available pages before exploring further.
integrationCode (server behavior depends on the code; today: Gu1 global sanctions).
Authentication
entityId.
JSON body
Entity UUID (must belong to your organization).
Integration / enrichment code. Supported today:
Other values return 400
global_gueno_sanctions_enrichment.Other values return 400
UNSUPPORTED_MONITORING_INTEGRATION.true— include in continuous monitoring when org and upstream allow (re-enable).false— exclude (same as legacymonitoringOptOut: true). At least one ofactiveorriskMatrixIdmust be sent.
Optional. Gu1 global sanctions only. UUID of a risk matrix in your org, or
null to clear the per-subscription override (daily screening then uses the entity risk matrix again, same as before).
When a UUID is set, only that matrix is used for rules triggered by monitoring (e.g. trigger_monitoring_completed after daily screening); the entity’s assigned matrix is not merged in for that run. Does not update entities.riskMatrixId.Error responses
| HTTP | Code (example) | When |
|---|---|---|
| 404 | ENTITY_NOT_FOUND | Entity not in org. |
| 400 | UNSUPPORTED_MONITORING_INTEGRATION | No handler for integrationCode, or riskMatrixId on an unsupported code. |
| 400 | INVALID_RISK_MATRIX | Matrix missing, archived, or not in org. |
Example — turn off Gu1 monitoring
Deprecated route
PATCH /entities/{id}/gueno-sanctions-monitoring-opt-out with { "monitoringOptOut" } is deprecated; use this endpoint with active: !monitoringOptOut.