> 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/dnk/api-dokumentation/diagrams-with-basic-flows/2.-graphql-subscription.md).

# 2. GraphQL-abonnement

Sekvensdiagrammet for GraphQL-abonnementer viser, hvordan man kan drage fordel af den hændelsesdrevne arkitektur, der er implementeret i GeoPard-kernen. Når der sker ændringer i de tilknyttede entiteter, udsender

GeoPard API'et hurtigt en hændelse, der registrerer de berørte entiteter og den tilhørende handling (`INSERT`, `MODIFY`, `REMOVE`). Disse abonnementer dækker et bredt spektrum af entiteter, herunder Farm, Field, SatelliteImage, SoilDataset, AsAppliedDataset, YieldDataset, TopographyMap, Notes osv.

GraphQL-abonnementet ([Anmodning 1 eller R1](https://docs.geopard.tech/geopard-tutorials/dnk/api-dokumentation/geopard-api-requests-overview/1.-subscription-get-events.md)) fungerer via en WebSocket, hvor alle hændelser leveres næsten i realtid, så ændringer kommunikeres med det samme.

{% hint style="danger" %}
Modtageren af abonnementshændelserne bør fungere som en simpel tjeneste, der videresender de modtagne hændelser til en efterfølgende tjeneste, hvor behandlingslogikken anvendes. Det er afgørende, at modtageren ikke selv udfører nogen behandlingsopgaver.
{% endhint %}

Hvis hændelser går tabt eller ikke modtages, kan brugerne desuden hente dem igen. Det gør man ved at udføre en GraphQL-forespørgsel, der er afgrænset til et bestemt datointerval og bestemte entiteter (User, Farm, Field), så tidligere hændelser kan gendannes fuldstændigt ([Anmodning 2 eller R2](https://docs.geopard.tech/geopard-tutorials/dnk/api-dokumentation/geopard-api-requests-overview/82.-query-restore-subscription-events.md)). Denne funktionalitet sikrer, at ingen oplysninger går tabt, og bevarer integriteten og konsistensen af brugerdataene.

<figure><img src="https://1581835146-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYICBELdyAXXebKAzfLOR%2Fuploads%2F8YoTw2Od4ykqav13zGp4%2Fimage.png?alt=media&amp;token=f9ba66ec-8172-40c6-a3b6-36fc0ecbb24b" alt=""><figcaption><p>Sekvensdiagram: Arbejde med abonnementshændelser</p></figcaption></figure>


---

# 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/dnk/api-dokumentation/diagrams-with-basic-flows/2.-graphql-subscription.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.
