Review Alerts

Alerts are the public operator work queue. The dashboard's Review workspace uses these same operations.

Build a queue

GET /v1/alerts supports cursor pagination plus filters for state, assignee, unassigned status, Check, Applicant, use case, overdue status, and search. Use GET /v1/alerts/summary for queue counters instead of downloading and counting every record.

curl "https://api.fideralabs.com/v1/alerts?state=new&unassigned=true&limit=50" \
  --header "Authorization: Bearer $FIDERA_API_KEY"

List assignment candidates with GET /v1/operators.

Assign or claim

Set assigned_to to an operator UUID. Set it to null to explicitly unassign.

curl "https://api.fideralabs.com/v1/alerts/$ALERT_ID" \
  --request PATCH \
  --header "Authorization: Bearer $FIDERA_API_KEY" \
  --header "Content-Type: application/json" \
  --data '{ "assigned_to": "00000000-0000-0000-0000-000000000000" }'

Investigate and escalate

Move work through the allowed state machine rather than updating local state optimistically. A rejected transition returns a structured client error.

{ "state": "investigating" }

Escalation records its timestamp and becomes available to the escalated queue. Overdue filtering uses the Alert SLA evidence.

Record a disposition

False-positive and confirmed-match dispositions require a human-readable reason and at least one structured evidence item:

{
  "state": "cleared_false_positive",
  "disposition_reason": "Date of birth and nationality conflict with the source entity.",
  "disposition_evidence": [
    {
      "field": "date_of_birth",
      "subject_value": "1990-01-01",
      "entity_value": "1971-04-18",
      "source": "customer_verified_identity"
    }
  ]
}

Do not put a broad investigation narrative in Fidera. Keep the narrative and case grouping in your system; attach the Fidera Alert and Check IDs.

Four-eyes approval

If four_eyes_required is true, the disposition is proposed but not finally approved by the first operator. A different supervisor or admin must perform the approval action. Fidera enforces actor separation; changing clients or calling the API directly cannot bypass it.

Read the immutable action history at GET /v1/alerts/{alert_id}/events.