---
title: "Close an alert event"
method: POST
path: "/v1/alert-events/{id}/close"
tags: ["alert-events"]
---

# Close an alert event

`POST /v1/alert-events/{id}/close`

## Request

- Base URL: `https://api.brixsignage.com`
- URL: `https://api.brixsignage.com/v1/alert-events/{id}/close`
- Auth: HTTP bearer

Manually close an alert event before it would close automatically on recovery. Access is checked against the screen where the alert fired.

**Notes.**
- The route-registry description names `alert-rule.edit`, but the route is gated by `screen.edit` at the event's location.

## Path parameters

- `id` string, required

## Response `200`

Success.

- object
  - `data` AlertEvent, required: One firing of an alert rule against a screen.
    - `id` string, required: Alert event id.
    - `code` string, required: What fired, e.g. `connection-lost`, `display-off`, `storage-critical`.
    - `severity` string, required: `info`, `warning` or `critical`.
    - `screenId` string, required
    - `screenName` string, required: `(unknown screen)` if the screen is gone.
    - `message` string, required
    - `nextAction` string, required: Suggested next step; may be empty.
    - `openedAt` string, required: ISO-8601 timestamp (UTC).
    - `closedAt` string, nullable, required: ISO-8601 timestamp (UTC).
    - `detail` object, nullable, required: Structured detail keyed by `kind` (`recovery`, `outage-history`, `network-unstable`, `display-off`), or null.
      - `kind` string, required

## Other responses

- `401`: Missing, expired or revoked bearer token.
- `403`: The token lacks the permission this operation needs (see `x-brix-permission`).
- `404`: No such event.
- `409`: `already_closed`.
- `5XX`: Server error. The body carries a `requestId` to quote to support.

---

[API](https://skmtc.dev/brixsignage/apis/brix-api.md) · [All operations](https://skmtc.dev/brixsignage/apis/brix-api/llms.txt) · [OpenAPI document](https://skmtc.dev/brixsignage/apis/brix-api/revisions/02fd3665dc7d?raw)