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

# 2. Naročnina GraphQL

Diagram zaporedja za naročnine GraphQL prikazuje, kako izkoristiti arhitekturo, ki temelji na dogodkih in je implementirana v jedru GeoPard. Ob vsaki spremembi povezanih entitet

API GeoPard nemudoma odda dogodek, ki zajame spremenjene entitete in ustrezno operacijo (`INSERT`, `MODIFY`, `REMOVE`). Obseg teh naročnin je širok in zajema vse entitete, kot so kmetija, polje, satelitski posnetek, nabor podatkov o tleh, nabor podatkov o izvedenih opravilih, nabor podatkov o pridelku, topografski zemljevid, opombe itd.

Naročnina GraphQL ([zahteva 1 ali R1](https://docs.geopard.tech/geopard-tutorials/svn/dokumentacija-api/geopard-api-requests-overview/1.-subscription-get-events.md)) deluje prek povezave WebSocket, po kateri se vsi dogodki prenašajo skoraj v realnem času, kar zagotavlja takojšnje obveščanje o vseh spremembah.

{% hint style="danger" %}
Prejemnik dogodkov naročnine naj deluje kot osnovna storitev, ki prejete dogodke posreduje naslednji storitvi, kjer se uporabi logika obdelave. Ključno je, da prejemnik sam ne izvaja nobenih opravil obdelave.
{% endhint %}

Poleg tega lahko uporabniki pridobijo dogodke, ki so bili spregledani ali izgubljeni. To storijo z izvedbo poizvedbe GraphQL za določeno časovno obdobje in entitete (uporabnik, kmetija, polje), s čimer omogočijo popolno obnovitev preteklih dogodkov ([zahteva 2 ali R2](https://docs.geopard.tech/geopard-tutorials/svn/dokumentacija-api/geopard-api-requests-overview/82.-query-restore-subscription-events.md)). Ta funkcionalnost zagotavlja, da se nobena informacija ne izgubi, ter ohranja celovitost in doslednost uporabniških podatkov.

<figure><img src="https://29491374-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>Diagram zaporedja: Delo z dogodki naročnine</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/svn/dokumentacija-api/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.
