# Get tracker events history via API

## Question

Can I get full history of tracker events (geofence exit, bracelet removal, etc.) via API?

## Answer

Yes.

Options:

* **Unread events only:** [Get all unread events](/docs/navixy-api/user-api/backend-api/guides/rules-notifications/work-with-notifications.md)
* **All events for a tracker over a time period:** [Events for specific trackers and time period](/docs/navixy-api/user-api/backend-api/guides/rules-notifications/work-with-notifications.md#events-for-specific-trackers-and-time-period)
* **All events for a user over a time period:** [All user events for a time period](/docs/navixy-api/user-api/backend-api/guides/rules-notifications/work-with-notifications.md#all-events-of-a-user-for-a-specific-time-period)

You can filter by event type codes, for example:

`events: ["inzone", "outzone"]`

### How to find event type codes

Call the event types list endpoint:

* [Event types list](/docs/navixy-api/user-api/backend-api/resources/commons/history/history_type.md)

Tips:

* Set `locale` to any supported language you need.
* Set `only_tracker_events=true` to list only tracker-related events.

### Implementation tip

You usually fetch event types once during development, then hardcode the event codes you need.

### Real-time notifications

If you want to build something like a live event feed, you can implement simple polling — query the API every few seconds.

## Links

* [Work with notifications](/docs/navixy-api/user-api/backend-api/guides/rules-notifications/work-with-notifications.md)
* [Event types list](/docs/navixy-api/user-api/backend-api/resources/commons/history/history_type.md)


---

# Agent Instructions: 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/get-tracker-events-history-via-api.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.