---
title: "ArchiveDeviceAlert"
method: PATCH
path: "/alerts/{id}/archive"
tags: ["Alerts"]
---

# ArchiveDeviceAlert

`PATCH /alerts/{id}/archive`

Archives an Alert. For more information, see our [nRF Cloud documentation on device alerts](https://docs.nordicsemi.com/bundle/nrf-cloud/page/Devices/MessagesAndAlerts/AlertsAndLogs/AlertsOverview.html).

## Path parameters

- `id` string, required — Universally unique identifier

## Response `200`

Ok

- ArchivedAlert
  - `id` string, required — Universally unique identifier
  - `deviceId` string, required — This is the canonical device id used in the device certificate, and as the MQTT client id.
  - `createdAt` string, date-time — HTML-encoded ISO-8601 date-time string denoting the start or end of a date range. If the string includes only a date, the time is the beginning of the day (00:00:00).
  - `receivedAt` string, date-time, required — HTML-encoded ISO-8601 date-time string denoting the start or end of a date range. If the string includes only a date, the time is the beginning of the day (00:00:00).
  - `statusChangedAt` string, date-time, required — HTML-encoded ISO-8601 date-time string denoting the start or end of a date range. If the string includes only a date, the time is the beginning of the day (00:00:00).
  - `statusChangedBy` string, required — Universally unique identifier
  - `status` 'ARCHIVED', required — ACTIVE: The alert is active and has not been resolved. ARCHIVED: The alert has been resolved and is no longer active.
  - `originalMessage` object, required — The original message sent from the device that triggered the alert.

---

[API](https://skmtc.dev/nrfcloud/apis/nrf-cloud-rest-api.md) · [All operations](https://skmtc.dev/nrfcloud/apis/nrf-cloud-rest-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/nrfcloud/nrf-cloud-rest-api/revisions/c4e56e458ebf/schema)