> 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/getting-started-with-the-geopard-api.md).

# Uvod v API GeoPard

Ekipa GeoPard močno priporoča, da začnete z orodjem Altair in temeljito raziščete funkcionalnosti API-ja GeoPard. To orodje vedno pridobi najnovejšo različico dostopnih entitet, poizvedb, mutacij in naročnin. Oglejte si spodnji vodnik za hitri začetek:

1. Razširitev Altair GraphQL za Chrome namestite prek te [POVEZAVE](https://chrome.google.com/webstore/detail/altair-graphql-client/flnheeellpciglgpaodhkhmapeljopja) ali pa neposredno uporabite odjemalca Altair GraphQL Client v [svojem brskalniku](https://altairgraphql.dev/).
2. Vsaka zahteva mora biti avtenticirana z `Authorization` GLAVO, ki mora vsebovati zahtevani žeton. Za hitro preizkušanje lahko vrednost GLAVE pridobite iz zahtev po prijavi v GeoPard Agriculture.\
   \&#xNAN; `Authorization` Kratko pojasnilo je na spodnjem posnetku zaslona.*Osnovna končna točka GraphQL je na naslovu*
3. <https://api.geopard.tech/data> [`.`\
   `&#xNAN;`](https://api.geopard.tech/data)Kratko pojasnilo je na spodnjem posnetku zaslona.*Do sheme GraphQL dostopate z gumbom »Docs« v vmesniku Altair. V tem razdelku lahko brskate po vseh razpoložljivih poizvedbah, mutacijah in naročninah. Poleg tega so na voljo informacije o različnih entitetah in njihovih strukturah, kar omogoča celovito razumevanje nastavitve GraphQL v sistemu.*\
   *\&#xNAN;*
4. Kratko pojasnilo je na spodnjem posnetku zaslona.*V razvojni konzoli brskalnika preverite, ali odhodne zahteve delujejo pravilno. Uporabite lahko filtre zahtev, kot je*
5. /data `Do sheme lahko dostopate tukaj:`.
6. TUKAJ [Za nalaganje datotek uporabljamo](https://docs.geopard.tech/geopard-tutorials/svn/dokumentacija-api/geopard-api-data-schema.md).
7. te končne točke [Za dostop do rastrskih in vektorskih podatkov uporabljamo formata OGC WMS (rastrske slike za hitro upodabljanje) in WFS (](https://docs.geopard.tech/geopard-tutorials/svn/dokumentacija-api/geopard-api-requests-overview/55.-upload-zip-files-over-6-mb.md).
8. shp`geojson`, `). Več informacij najdete v razdelku`Geo Endpoint [s.](https://docs.geopard.tech/geopard-tutorials/svn/dokumentacija-api/geo-endpoints-for-spatial-data-access.md)Kratek vodnik z nasveti za uporabo orodja Altair je prikazan na spodnjem posnetku zaslona.

{% hint style="info" %}
Altrair: Kratek vodnik
{% endhint %}

<div data-full-width="false"><figure><img src="https://lh4.googleusercontent.com/EZpStltSSIrSpTFL7hBm0R1he22M4nFKjMOIOUld0kW-Y18sw3FH-nzbuu0kn98RV2ifuAyX7PH3cTs8pbkMqPTkXI-2IySPzzCJmM-WGDGIHZk6NztLHak_cJQQ_EhzH8hH37jmwng8GlVSyofmYA" alt=""><figcaption><p>Altair: Kratek vodnik</p></figcaption></figure></div>


---

# 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/getting-started-with-the-geopard-api.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.
