> For the complete documentation index, see [llms.txt](https://docs.geopard.tech/geopard-tutorials/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.geopard.tech/geopard-tutorials/fr/documentation-api/vue-densemble-des-requetes-de-lapi-geopard/1.-abonnement-obtenir-les-evenements.md).

# 1. Abonnement : obtenir les événements

Suivre les abonnements lorsque `INSERT`/`MODIFY`/`REMOVE` des actions se produisent avec "Farm", "Field", "FieldSatelliteImage", "RasterAnalysisMap", "VectorAnalysisMap", et autres entités.

Le mécanisme d'abonnement est construit sur MQTT et WebSocket. Nous recommandons de commencer l'intégration en lisant le [article AWS AppSync Subscription](https://docs.aws.amazon.com/appsync/latest/devguide/real-time-websocket-client.html). 

{% hint style="info" %}
Les événements d'abonnement sont envoyés dès que l'événement se produit dans le backend GeoPard.
{% endhint %}

{% hint style="info" %}
Chaque événement d'abonnement possède une identification unique nommée `uuid`, ce qui est utile pour filtrer les événements traités et manquants demandés depuis [82. Requête : Restaurer les événements d'abonnement](/geopard-tutorials/fr/documentation-api/vue-densemble-des-requetes-de-lapi-geopard/82.-requete-restaurer-les-evenements-dabonnement.md).
{% endhint %}

{% code lineNumbers="true" %}

```graphql
subscription FollowPlatformEvent {
  followPlatformEvent(userUuid: "<placeholder_of_user_uuid>") {
    uuid
    userUuid
    action
    nodePath {
      entity
      uuid
    }
  }
}
```

{% endcode %}


---

# 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://docs.geopard.tech/geopard-tutorials/fr/documentation-api/vue-densemble-des-requetes-de-lapi-geopard/1.-abonnement-obtenir-les-evenements.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.