Receive alerts and review incidents

Use incidents:read for alert and incident reads. Updating incident review state requires incidents:acknowledge and access to the incident’s camera. Delivery consumers use their separate alerts:deliver authority.

Read recent activity

curl --fail-with-body --silent --show-error \
  --header "Authorization: Bearer ${EOI_SERVICE_TOKEN}" \
  "${EOI_API_BASE_URL}/alerts?limit=100"

List alerts returns an array of recent alert resources. For a review queue, use List incidents and its status, time, camera, severity, limit, and offset filters.

Review an incident

1. Select an incident ID from the list response and call Get incident.
2. Retrieve incident evidence and inspect the snapshot or recording resources available for that event.
3. Add a review note with Add incident note.
4. Submit Update incident with the supported review-state fields and required revision header.
5. Read incident history to confirm the recorded change.

Deliver alerts to another system

Use a registered consumer’s claim and acknowledgment resources for delivery processing. Persist the claim and the result of your downstream handling before acknowledging it. Consult the consumer operations for the exact request and response models.

For notification destinations, use the notification profiles reference. Customer approval and controlled tests have separate revision and request-ID requirements. An accepted delivery indicates transport acceptance.