> 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/es/monitorizacion-e-informes/verkada-classic-alarms-monitoring-certificate.md).

# Certificado de monitorización de Alarmas clásicas de Verkada

Obtén un certificado que indique que tu sitio de alarma está monitorizado

{% hint style="success" %}
Verkada anunció el fin global de la venta (1 de agosto de 2026) y el fin de vida (1 de agosto de 2027) de Classic Alarms. Los clientes elegibles pueden actualizarse a New Alarms sin costo hasta el 31 de enero de 2027. Visite [Verkada.com/alarms/upgrade](https://www.verkada.com/alarms/upgrade) para comenzar.
{% endhint %}

Un Certificado de monitoreo de alarma confirma que Verkada supervisa profesionalmente su sistema de alarma y sirve como comprobante para su proveedor de seguros.

***

### Obtenga el certificado <a href="#obtain-the-certificate" id="obtain-the-certificate"></a>

[Póngase en contacto con el equipo de soporte de Verkada](https://help.verkada.com/command/need-help/contact-verkada-support) con la siguiente información para solicitar su certificado:

* **Nombre del sitio:** Nombre exacto que aparecerá en el certificado.
* **Dirección del sitio:** Dirección completa (incluida la ciudad, el estado, el código postal y el país de la ubicación monitorizada).
* **Fecha de inicio del monitoreo:** La fecha en que Verkada comenzó a monitorear el sitio.

{% hint style="danger" %}
Las solicitudes suelen procesarse en **1–2 días hábiles.**
{% endhint %}


---

# 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/es/monitorizacion-e-informes/verkada-classic-alarms-monitoring-certificate.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.