> For the complete documentation index, see [llms.txt](https://help.verkada.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.verkada.com/classic-alarms/configuration/verkada-alarm-api.md).

# Verkada Classic Alarms API

The Verkada Classic Alarms API integrates with third party platforms

{% hint style="success" %}
Verkada announced the global End of Sale (August 1, 2026) and End of Life (August 1, 2027) for Classic Alarms. Eligible customers can upgrade to New Alarms at no charge through January 31, 2027. Visit [Verkada.com/alarms/upgrade](https://www.verkada.com/alarms/upgrade) to get started.
{% endhint %}

The Alarm API enables you to programmatically extract data and automate tasks via third-party platforms securely and at scale. The API is REST-based, returns JSON-encoded responses, and uses standard HTTP response codes. Comprehensive documentation about the Alarm API is available at

{% hint style="info" %}
See our [API docs](https://apidocs.verkada.com/) for more information.
{% endhint %}

***

## Available endpoints

* [**Sites endpoint (GET)**](https://apidocs.verkada.com/reference/getalarmssitesviewv1): Read-only endpoint that returns information about sites in your Verkada alarm organization.
* [**Devices endpoint (GET)**](https://apidocs.verkada.com/reference/getalarmsdevicesviewv1): Read-only endpoint that returns information about devices in your Verkada alarm organization/sites.
* [**Site State Change webhook**:](https://apidocs.verkada.com/reference/alarm-webhook-object) Allows a third-party platform to subscribe to any site state change events within your Verkada alarm organization. These events include arm/disarm, alarm, etc.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.verkada.com/classic-alarms/configuration/verkada-alarm-api.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.