> 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/api-docs/diagrams-with-basic-flows/2.-graphql-subscription.md).
# 2. GraphQL Subscription
The sequence diagram for GraphQL Subscriptions illustrates how to benefit from the event-driven architecture implemented in the GeoPard core. Upon any changes to the linked entities, the
GeoPard API promptly emits an event capturing the impacted entities and the corresponding operation (`INSERT`, `MODIFY`, `REMOVE`). The scope of these subscriptions is expansive, covering all entities such as Farm, Field, SatelliteImage, SoilDataset, AsAppliedDataset, YieldDataset, TopographyMap, Notes, etc.
The GraphQL Subscription ([Request 1 or R1](/geopard-tutorials/api-docs/geopard-api-requests-overview/1.-subscription-get-events.md)) operates on a WebSocket where all events are delivered in almost real-time, ensuring immediate communication of any changes.
{% hint style="danger" %}
The receiver of the subscription events should function as a basic service, responsible for routing the received events to a subsequent service where processing logic is applied. It is crucial that this receiver doesn't perform any processing tasks itself.
{% endhint %}
Moreover, should there be any missed or lost events, users have the capability to retrieve them. This is achieved by executing a GraphQL query tailored for a specific date range and entities (User, Farm, Field), effectively enabling a complete recovery of past events ([Request 2 or R2](/geopard-tutorials/api-docs/geopard-api-requests-overview/82.-query-restore-subscription-events.md)). This level of functionality ensures no information is lost, maintaining the integrity and consistency of user data.
Sequence diagram: Workk with Subscription Events
---
# 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/api-docs/diagrams-with-basic-flows/2.-graphql-subscription.md?ask=&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.
