> 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/qna/apis.md).

# APIs

This section provides guidance for integrating with Navixy's APIs and real-time data streams. Learn authentication methods, data retrieval patterns, and best practices for building custom applications, dashboards, and system integrations. The guides cover everything from basic API authentication to advanced real-time tracking implementations.

Essential for developers building on the Navixy platform, whether you're creating a custom mobile app, integrating GPS tracking into existing software, automating fleet operations, or extracting data for analytics. Topics include choosing between WebSockets and REST polling, handling pagination, working with events and sensors, and implementing secure authentication.

## Browse guides

<details>

<summary>Authentication and session handling</summary>

* [User session hash vs admin panel hash vs API key](/docs/qna/apis/user-session-hash-vs-admin-panel-hash-vs-api-key.md)

</details>

<details>

<summary>Real-time and telemetry</summary>

* [WebSockets vs get\_states API for real-time tracking data](/docs/qna/apis/websockets-vs-get_states-api-for-real-time-tracking-data.md)
* [Get relevant telemetry in one API call (get\_state)](/docs/qna/apis/get-relevant-telemetry-in-one-api-call-get_state.md)
* [Retrieve latest sensor readings for multiple trackers](/docs/qna/apis/retrieve-latest-sensor-readings-for-multiple-trackers.md)

</details>

<details>

<summary>Errors and troubleshooting</summary>

* [API error codes and HTTP statuses](/docs/qna/apis/api-error-codes-and-http-statuses.md)
* [Empty list in API response](/docs/qna/apis/empty-list-in-api-response.md)

</details>

<details>

<summary>Location and geocoding</summary>

* [Batch geocoding support for search\_location](/docs/qna/apis/batch-geocoding-support-for-search_location.md)
* [Identify a usual / longest parking location via API](/docs/qna/apis/identify-a-usual-longest-parking-location-via-api.md)

</details>

<details>

<summary>Events and remote control</summary>

* [Get tracker events history via API](/docs/qna/apis/get-tracker-events-history-via-api.md)
* [Track when output control was changed via API](/docs/qna/apis/track-when-output-control-was-changed-via-api.md)
* [Update tracker label via API](/docs/qna/apis/update-tracker-label-via-api.md)

</details>

<details>

<summary>Video</summary>

* [API to retrieve videos from the platform](/docs/qna/apis/api-to-retrieve-videos-from-the-platform.md)

</details>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://navixy.com/docs/qna/apis.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.