Alert events API

Alert events endpoints in the Brix REST API: 2 operations (GET, POST), with auth, permissions and curl examples.

View as Markdown

Base URL https://api.brixsignage.com. Send Authorization: Bearer $BRIX_API_KEY unless an operation says No auth. The permission chip names what the key must hold. See Authentication and scopes, Errors and rate limits and Pagination.

GET/v1/alert-events

Bearer token screen.view

List alerts that have fired against your screens, each combined with the screen's name. This endpoint is read-only: alerts open automatically when a condition is detected and close automatically on recovery. Only currently open alerts are returned, as a limited list, so a long history does not push them out. Open events (up to 300, newest first) followed by recently closed ones (up to 300). Not paginated. **Notes.** - The route-registry description names alert-rule.view, but the route is gated by screen.view; screen.view is what a key needs.

curl "https://api.brixsignage.com/v1/alert-events" \
  -H "Authorization: Bearer $BRIX_API_KEY"

Response 200 Success.

FieldTypeDescription
dataarray of AlertEvent
data[].idstringAlert event id.
data[].codestringWhat fired, e.g. `connection-lost`, `display-off`, `storage-critical`.
data[].severitystring`info`, `warning` or `critical`.
data[].screenIdstring
data[].screenNamestring`(unknown screen)` if the screen is gone.
data[].messagestring
data[].nextActionstringSuggested next step; may be empty.
data[].openedAtstringISO-8601 timestamp (UTC).
data[].closedAtstring | nullNull while open.
data[].detailobject | nullStructured detail keyed by `kind` (`recovery`, `outage-history`, `network-unstable`, `display-off`), or null.

Response 401 Missing, expired or revoked bearer token.

FieldTypeDescription
errorstringMachine-readable code: `unauthorized`, `forbidden`, `not_found`, `validation_error`, `conflict`, `rate_limited`, `internal_error`, …
messagestringHuman-readable explanation. Safe to show an operator.
requestIdstringPresent on 5xx: quote it to support.

Response 403 The token lacks the permission this operation needs (see `x-brix-permission`).

FieldTypeDescription
errorstringMachine-readable code: `unauthorized`, `forbidden`, `not_found`, `validation_error`, `conflict`, `rate_limited`, `internal_error`, …
messagestringHuman-readable explanation. Safe to show an operator.
requestIdstringPresent on 5xx: quote it to support.

Response 5XX Server error. The body carries a `requestId` to quote to support.

FieldTypeDescription
errorstringMachine-readable code: `unauthorized`, `forbidden`, `not_found`, `validation_error`, `conflict`, `rate_limited`, `internal_error`, …
messagestringHuman-readable explanation. Safe to show an operator.
requestIdstringPresent on 5xx: quote it to support.

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

Bearer token screen.edit

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.

ParameterInTypeRequiredDescription
idpathstringyesAlert event id.
curl -X POST "https://api.brixsignage.com/v1/alert-events/{id}/close" \
  -H "Authorization: Bearer $BRIX_API_KEY"

Response 200 Success.

FieldTypeDescription
dataAlertEventOne firing of an alert rule against a screen.
data.idstringAlert event id.
data.codestringWhat fired, e.g. `connection-lost`, `display-off`, `storage-critical`.
data.severitystring`info`, `warning` or `critical`.
data.screenIdstring
data.screenNamestring`(unknown screen)` if the screen is gone.
data.messagestring
data.nextActionstringSuggested next step; may be empty.
data.openedAtstringISO-8601 timestamp (UTC).
data.closedAtstring | nullNull while open.
data.detailobject | nullStructured detail keyed by `kind` (`recovery`, `outage-history`, `network-unstable`, `display-off`), or null.

Response 401 Missing, expired or revoked bearer token.

FieldTypeDescription
errorstringMachine-readable code: `unauthorized`, `forbidden`, `not_found`, `validation_error`, `conflict`, `rate_limited`, `internal_error`, …
messagestringHuman-readable explanation. Safe to show an operator.
requestIdstringPresent on 5xx: quote it to support.

Response 403 The token lacks the permission this operation needs (see `x-brix-permission`).

FieldTypeDescription
errorstringMachine-readable code: `unauthorized`, `forbidden`, `not_found`, `validation_error`, `conflict`, `rate_limited`, `internal_error`, …
messagestringHuman-readable explanation. Safe to show an operator.
requestIdstringPresent on 5xx: quote it to support.

Response 404 No such event.

FieldTypeDescription
errorstringMachine-readable code: `unauthorized`, `forbidden`, `not_found`, `validation_error`, `conflict`, `rate_limited`, `internal_error`, …
messagestringHuman-readable explanation. Safe to show an operator.
requestIdstringPresent on 5xx: quote it to support.

Response 409 `already_closed`.

FieldTypeDescription
errorstringMachine-readable code: `unauthorized`, `forbidden`, `not_found`, `validation_error`, `conflict`, `rate_limited`, `internal_error`, …
messagestringHuman-readable explanation. Safe to show an operator.
requestIdstringPresent on 5xx: quote it to support.

Response 5XX Server error. The body carries a `requestId` to quote to support.

FieldTypeDescription
errorstringMachine-readable code: `unauthorized`, `forbidden`, `not_found`, `validation_error`, `conflict`, `rate_limited`, `internal_error`, …
messagestringHuman-readable explanation. Safe to show an operator.
requestIdstringPresent on 5xx: quote it to support.