> 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/swe/api-dokumentation/oversikt-over-geopard-api.md).
# Översikt över GeoPard API
Senaste uppdatering: 10 juli 2023
GeoPard är en precisionsjordbruksplattform med alla funktioner tillgängliga via API
GeoPard API erbjuder både GraphQL- och REST-endpoints för smidig interaktion. Som både ett passivt och aktivt gränssnitt gör det det möjligt för andra applikationer att programmatiskt begära att analytiska derivat skapas och att ta emot uppdateringar kopplade till komplex databehandling.
Via GeoPard API är alla rådatauppsättningar – inklusive skörd, maskiner, jordprovtagning och skannrar, satellitbilder och topografi – liksom analytiska derivat som skördzoner, ekvationskartor, rekommendationer och rasterytor, lätt tillgängliga direkt ur lådan.
GeoPard API stöder olika renderingsalternativ för geospatial data och hanterar både Raster (`jpg`, `png`, `geotiff`) och Vektor (`shp`, `geojson`, `isoxml`)-format. För en heltäckande översikt av API:t, se vårt [blogginlägg](https://geopard.tech/blog/upkdhsnyk1-precision-agriculture-api/).
---
# 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/swe/api-dokumentation/oversikt-over-geopard-api.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.
