> For the complete documentation index, see [llms.txt](https://navixy.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://navixy.com/docs/navixy-api/user-api/guides/data-retrieval.md).

# Data retrieval

Worked examples of getting trackers, tracks, sensor readings, and reports out of the Navixy platform.

Reading data out of the platform almost always takes more than one call: you find the tracker, then ask what it did, then ask for the detail. These guides walk those sequences end to end, with the calls in order and the reasoning for each parameter.

* [Getting list of GPS trackers](/docs/navixy-api/user-api/guides/data-retrieval/get-tracker-list.md): the first call most integrations make, and the one every other guide starts from.
* [Getting track points](/docs/navixy-api/user-api/guides/data-retrieval/get-track-points.md): from a tracker to its trips, and from a trip to the raw points behind it.
* [Retrieving sensor and counter data](/docs/navixy-api/user-api/guides/data-retrieval/sensor-data.md): reading what a device measured alongside its location.
* [Obtaining report information](/docs/navixy-api/user-api/guides/data-retrieval/obtain-reports.md): generating a report and collecting the result, which is asynchronous.


---

# 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://navixy.com/docs/navixy-api/user-api/guides/data-retrieval.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.