> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/products/integrations/video-management-systems/axis-alarms-and-events-interface.md).

# Axis Alarms and Events Interface

{% hint style="warning" %}
**Events and alarms only.** This integration does **NOT** include a video-viewing interface.
{% endhint %}

The Axis integration shares alarms and events between **Axis VAPIX** and Command Centre in both directions. On an event or alarm in Command Centre, an API string can be sent to a specified **Axis Encoder**. Axis events can likewise be surfaced in Command Centre.

Hardware and SDK versions supported are listed in the release note (Axis Alarms and Events v8.20).

{% hint style="warning" %}
Gallagher tests each integration with a small selection of cameras and can only guarantee those. Support for other cameras depends primarily on the VMS's SDK. Check with the VMS vendor's technical support for a given model.
{% endhint %}

***

🔗 **Related**

* [Video Management Systems](/knowledge-hub/products/integrations/video-management-systems.md). The other VMS integrations.


---

# 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.security.gallagher.com/knowledge-hub/products/integrations/video-management-systems/axis-alarms-and-events-interface.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.