> 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.md). # Guides and examples Whole tasks worked end to end, with the calls in the order an integration makes them. The reference tells you what one operation does. These guides tell you which operations to call, in what order, and why: getting a tracker's track points takes three calls, and a report is generated, retrieved once it is ready, then deleted. Start with [Getting list of GPS trackers](/docs/navixy-api/user-api/guides/data-retrieval/get-tracker-list.md) if you are new to the API. Almost every other guide begins from a tracker ID. ## [Data retrieval](/docs/navixy-api/user-api/guides/data-retrieval.md) * [Getting list of GPS trackers](/docs/navixy-api/user-api/guides/data-retrieval/get-tracker-list.md): the first call most integrations make, and where the other guides start. * [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. ## [Device management](/docs/navixy-api/user-api/guides/device-management.md) * [Activate device](/docs/navixy-api/user-api/guides/device-management/activate-device.md): registering a GPS device or a mobile app on the Navixy platform. * [Sending commands to a GPS tracker via IP protocol (OTA)](/docs/navixy-api/user-api/guides/device-management/send-commands.md): reconfiguring a device remotely instead of physically. * [Tracking stationary objects with BLE tags](/docs/navixy-api/user-api/guides/device-management/ble-beacons.md): using radio tags for objects that carry no device of their own. ## [Places](/docs/navixy-api/user-api/guides/places.md) * [Managing geofences](/docs/navixy-api/user-api/guides/places/manage-geofences.md): creating areas and using them to limit where a rule applies. * [Managing POIs](/docs/navixy-api/user-api/guides/places/manage-pois.md): creating the client sites and depots that tasks are assigned against. ## [Rules and notifications](/docs/navixy-api/user-api/guides/rules-notifications.md) * [Using rules](/docs/navixy-api/user-api/guides/rules-notifications/use-rules.md): defining the conditions the platform watches for. * [Working with notifications](/docs/navixy-api/user-api/guides/rules-notifications/work-with-notifications.md): reading the events a rule logged, and how they are delivered. * [Receiving push notifications in your app](/docs/navixy-api/user-api/guides/rules-notifications/get-push-notifications.md): getting events to an app without polling for them. ## [Field service management](/docs/navixy-api/user-api/guides/field-service-management.md) * [How to create and assign tasks](/docs/navixy-api/user-api/guides/field-service-management/manage-tasks.md): the starting point, and what the other three build on. * [Changing employee statuses](/docs/navixy-api/user-api/guides/field-service-management/change-task-statuses.md): recording what an employee is currently doing. * [Using task forms](/docs/navixy-api/user-api/guides/field-service-management/create-forms.md): collecting structured information when a task is completed. * [Working with check-ins](/docs/navixy-api/user-api/guides/field-service-management/check-ins.md): recording what an employee reported from a location. ## [Fleet management](/docs/navixy-api/user-api/guides/fleet-management.md) * [Managing vehicles and service works](/docs/navixy-api/user-api/guides/fleet-management/service-works.md): the vehicle record, and the maintenance due against it. * [Using driver journals](/docs/navixy-api/user-api/guides/fleet-management/driver-journals.md): categorising trips so transport use splits between business and private. * [Using tags](/docs/navixy-api/user-api/guides/fleet-management/use-tags.md): labelling across entity types so related things can be found together. ## Raw IoT Data * [Requesting Raw IoT Data](/docs/navixy-api/user-api/guides/raw-data.md): reading unprocessed device data through the [Raw IoT Data API](/docs/navixy-api/user-api/resources/data-warehouse-api.md), which has its own base URL and specification. --- # 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.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.