Skip to content
EyesOnItDocumentation6.1

Acknowledge alert delivery

POST /api/v1/alert-consumers/{consumer_id}/acknowledgments

Access

Section titled “Access”

Authentication options declared in the contract include user cookie session or bearer service token.

The shared authentication policy requires alerts:deliver. Resource access also depends on the caller’s role, organization, camera grants, and the operation’s validation.

Authentication and permissions explains tokens, cookies, CSRF, and workspace context.

Parameters

Section titled “Parameters”
Name Location Required Type Description and constraints
consumer_id path Yes string (uuid)
X-EyesOnIt-Session-Id header No string (uuid) The sessionId the caller expects. Required when switching workspaces and for cookie requests after workspace rotation. A mismatched value returns 409 with X-EyesOnIt-Workspace-Changed: 1. Bootstrap with getCurrentPrincipal; never replay a mutation automatically after changing context. Bearer clients do not use this header.
X-CSRF-Token header No string Required for unsafe requests authenticated by CookieSession; ignored for bearer clients. minimum length 32. maximum length 256

Request body

Section titled “Request body”

Required.

application/json — AlertAcknowledgment.

Field Type Required Description and constraints
leaseToken string (uuid) Yes
sequence integer (int64) Yes minimum 1.0
alertId string (uuid) Yes
disposition string Yes values "submitted", "mapping_unavailable"

cURL request template

Section titled “cURL request template”

Set the connection variables described in Get started. Replace each additional EOI_… variable with the parameter value for this request. Prepare the body file using the request schema above. This template sends the request when run.

Terminal window
curl --fail-with-body --silent --show-error \
  --request POST \
  --header "Authorization: Bearer ${EOI_SERVICE_TOKEN}" \
  --header "Content-Type: application/json" \
  --data-binary @request.json \
  "${EOI_API_BASE_URL}/alert-consumers/${EOI_CONSUMER_ID}/acknowledgments"

Contract responses

Section titled “Contract responses”

The table records responses declared by the OpenAPI contract. See Errors and status codes for the runtime error envelope and shared failures.

Status Description Media type Body
200 Successful Response application/json AlertConsumerResponse
422 Validation Error application/json HTTPValidationError

Operation identifier acknowledgeAlertDelivery. Browse Alerts and consumers.

Image preview