> 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/fr/surveillance-et-rapports/verkada-classic-alarms-monitoring-certificate.md).

# Certificat de surveillance Verkada Classic Alarms

Obtenez un certificat attestant que votre site d’alarme est surveillé

{% hint style="success" %}
Verkada a annoncé la fin mondiale de la vente (1er août 2026) et la fin de vie (1er août 2027) des alarmes classiques. Les clients éligibles peuvent passer aux nouvelles alarmes sans frais jusqu’au 31 janvier 2027. Consultez [Verkada.com/alarms/upgrade](https://www.verkada.com/alarms/upgrade) pour commencer.
{% endhint %}

Un certificat de surveillance d’alarme confirme que Verkada surveille professionnellement votre système d’alarme et sert de preuve pour votre assureur.

***

### Obtenir le certificat <a href="#obtain-the-certificate" id="obtain-the-certificate"></a>

[Contactez le service d’assistance de Verkada](https://help.verkada.com/command/need-help/contact-verkada-support) avec les informations suivantes pour demander votre certificat :

* **Nom du site :** Nom exact à faire figurer sur le certificat.
* **Adresse du site :** Adresse complète (y compris la ville, l’État, le code postal et le pays du site surveillé).
* **Date de début de la surveillance :** Date à laquelle Verkada a commencé à surveiller le site.

{% hint style="danger" %}
Les demandes sont généralement traitées sous **1 à 2 jours ouvrés.**
{% 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/fr/surveillance-et-rapports/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.