Remediation
Submit an externally-screened alert for AI-powered remediation
Behavior
- Accepts an alert with subject profile and hits that you have already screened externally
- Processing is asynchronous — returns an
idimmediately, remediation runs in the background - Results are retrieved via Get Alert using the returned
id - Triggers an
alert_remediatedwebhook when complete (see Webhooks)
Workflow
After submitting, the system will:- Validate the request and persist the alert
- Return
{ "id": "..." }with status201 - Enrich each hit (registry, web search, articles) based on your configured enrichments
- Run entity resolution and the rule engine against your configured rules and segments
- Generate evidence reports and summaries for each hit
- Trigger the
alert_remediatedwebhook
id to:
- Retrieve full results with GET /name-screenings/alerts/
- Correlate with webhook notifications
Authorizations
Body
Provider reference for the alert (e.g. case ID from your screening provider).
"WC-CASE-2026-001"
Subject profile as label/value pairs. Freeform labels — the AI uses LLM-based extraction.
1Screening hits to remediate. At least one required.
1Your own client reference for the same alert (e.g. internal case number).
"INTERNAL-42"
Response
Alert accepted for remediation
Alert ID. Use with GET /v1/name-screenings/alerts/{id} to retrieve results.
"550e8400-e29b-41d4-a716-446655440000"
Provider reference (echoed back).
"WC-CASE-2026-001"
Client reference (echoed back), or null if not provided.
"INTERNAL-42"
Submitted hits with references.