Your API key:

All requests below will use this key. Your API key is sent directly to api.cueapi.ai and never stored by the docs site.

POST/v1/alerts/{alert_id}/acknowledge

Acknowledge Alert

Mark an alert as acknowledged by the on-call user. Idempotent.

Marks an alert as acknowledged by the authenticated user. Acknowledging stops further reminders for the same incident and surfaces the ack timestamp on dashboards and alert webhook payloads.

Idempotent — acknowledging an already-acknowledged alert returns 200 with the original ack timestamp.

Request

bash

curl -X POST https://api.cueapi.ai/v1/alerts/3ab7c2d1-9f4e-4d12-9a35-7e8f1c4b6a82/acknowledge \
  -H "Authorization: Bearer cue_sk_YOUR_KEY"

Response

json

{
  "id": "3ab7c2d1-9f4e-4d12-9a35-7e8f1c4b6a82",
  "cue_id": "cue_xyz",
  "execution_id": "exec_abc",
  "alert_type": "consecutive_failure",
  "severity": "high",
  "message": "3 consecutive failures on cue daily-sync",
  "metadata": {"failure_count": 3, "first_failure_at": "..."},
  "acknowledged": true,
  "created_at": "2026-04-19T18:30:00Z"
}

Errors

Status	Code	Cause
401	`not_authenticated`	Missing/invalid bearer token
404	`alert_not_found`	`alert_id` doesn't exist or doesn't belong to the authenticated user

Behavior after acknowledgement

The alert's acknowledged flag becomes true.
The alert is excluded from GET /v1/alerts?acknowledged=false filters by default.
If the underlying cue continues to fail, a new alert is generated (a separate row) — acknowledging does not silence the cue itself.
Alert webhook deliveries triggered by future failures include previous_acknowledged_at in the payload metadata so on-call automation can correlate.

POST/v1/alerts/{alert_id}/acknowledge

Try it

Replace path parameters (e.g. {cue_id}) in the URL before sending.

Request Body

Enter your API key above to send requests

Previous← List Alerts NextRegister →