Get Alert History

alertHistory returns a list of previously triggered alerts for the Bolt Cloud account.
Each entry contains the time, message, device ID, and alert name.

Useful for:

• Quickly reviewing recent alerts

• Showing alert activity to users in dashboards

• Debugging when and how often alerts are firing

Endpoint

https://cloud.boltiot.com/remote/{API_KEY}/alertHistory
 
https://cloud.boltiot.com/remote/{API_KEY}/alertHistory?limit={LIMIT}

Replace:

• {API_KEY} with your Bolt Cloud API key

• {LIMIT} (optional) with the number of records to fetch (1–500)

If limit is not passed, the API returns 500 entries by default.

Note: This endpoint can return a large amount of data and may take some time to respond.
Always use the limit parameter wherever possible.

Response Format

The response is a JSON object with the following fields:

Each entry in value contains:

Example:

Request

https://cloud.boltiot.com/remote/44b2de.../alertHistory?limit=10

Response

{
  "value": [
    {
      "time": "2024-01-29T15:05:41.141999Z",
      "message": "BOLT14619919 is offline. {device_name} is now {status}.",
      "device": "BOLT14619919",
      "alert_name": "EMAIL_STATUS"
    },
    {
      "time": "2024-01-29T15:05:43.571000Z",
      "message": "BOLT14619919 is offline. {device_name} is now {status}.",
      "device": "BOLT14619919",
      "alert_name": "PUSH_STATUS"
    }
    // ...up to `limit` entries
  ],
  "success": 1
}

Notes for Developers and Agents

• Use limit to control the number of entries returned (1–500).

• If limit is omitted, 500 entries are returned.

• This endpoint is intended for summarized history:

  • Time of alert

  • Message content

  • Device ID

  • Alert name

• For deeper debugging (delivery responses, snapshot of alert configuration at trigger time), use alertHistoryRaw.

Error Handling

If the API key is invalid or the request fails, success will be 0.

Example:

{
  "success": 0
}

Recommendation: Check success before evaluating value.