> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.chrt.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.chrt.com/_mcp/server.

# Tracker API

> Endpoint reference for managing chrt tracking devices, tracking sessions, and per-device telemetry — including public read endpoints for shared sessions.

Every workflow you can do in the chrt UI for tracking — registering a
device, creating a session, terminating it, reading telemetry — is also
available over the chrt API. Use this page as the index of relevant
endpoints; the full request and response schemas live in the API
reference.

> **Note**
>
> All endpoints require an API key unless explicitly marked **public**.
> Public endpoints exist only after a session has been made public in
> the UI or via the [update session](https://docs.chrt.com/api-reference/api-reference/tracking/sessions/update-v-1)
> endpoint. See [the public-session warning](#making-a-session-public) below.

## Devices

Manage the hardware records registered to your organization.

* [Register a device](https://docs.chrt.com/api-reference/api-reference/tracking/devices/register-to-org-v-1) — add a new device by MAC address.
* [Update a device](https://docs.chrt.com/api-reference/api-reference/tracking/devices/update-v-1) — change type, external reference, or comments.
* [Archive a device](https://docs.chrt.com/api-reference/api-reference/tracking/devices/archive-v-1) — remove from the active list without deleting history.
* [Pause a device](https://docs.chrt.com/api-reference/api-reference/tracking/devices/pause-v-1) — stop accepting pings for this device.
* [Unpause a device](https://docs.chrt.com/api-reference/api-reference/tracking/devices/unpause-v-1) — resume after a pause.
* [Get device](https://docs.chrt.com/api-reference/api-reference/tracking/devices/get-v-1) — fetch a single device by ID.
* [List devices](https://docs.chrt.com/api-reference/api-reference/tracking/devices/list-v-1) — paginate, filter, and sort devices.

## Sessions

A **tracking session** is the bounded recording of pings for one device.
See [Standalone trackers](/trackers/standalone) for the UI flow and
[Tracking concepts](/docs/concepts/tracking) for the data model.

* [Create session](https://docs.chrt.com/api-reference/api-reference/tracking/sessions/create-session-v-1) — start a new recording for a device.
* [Update session](https://docs.chrt.com/api-reference/api-reference/tracking/sessions/update-v-1) — change metadata, flight assignments, or visibility.
* [Terminate session](https://docs.chrt.com/api-reference/api-reference/tracking/sessions/terminate-v-1) — permanently stop recording. Cannot be undone.
* [Get session](https://docs.chrt.com/api-reference/api-reference/tracking/sessions/get-v-1) — fetch a single session.
* [List sessions](https://docs.chrt.com/api-reference/api-reference/tracking/sessions/list-v-1) — paginate, filter (active vs. terminated), and sort.

## Session telemetry by device

Read raw pings and last-known location for the active session on a
device. Two flavors: authenticated endpoints (any session on your org's
devices) and **public** endpoints (only for sessions that have been
made public).

* [Last seen](https://docs.chrt.com/api-reference/api-reference/tracking/timeseries/session-by-device/last-seen-v-1) — the most recent ping for the device's active session.
* [Data points](https://docs.chrt.com/api-reference/api-reference/tracking/timeseries/session-by-device/data-points-v-1) — paginated ping history.
* [Last seen (public)](https://docs.chrt.com/api-reference/api-reference/tracking/timeseries/session-by-device/last-seen-public-v-1) — no auth, public sessions only.
* [Data points (public)](https://docs.chrt.com/api-reference/api-reference/tracking/timeseries/session-by-device/data-points-public-v-1) — no auth, public sessions only.

## Creating a session

You can create a session two ways:

* **In the UI.** Open
  [chrt.com/tracking/devices](https://chrt.com/tracking/devices) and use
  **+ Create Session** on a device row, or open
  [chrt.com/tracking/sessions](https://chrt.com/tracking/sessions) and
  click **+ Create Session**.
* **Over the API.** Call the
  [create session](https://docs.chrt.com/api-reference/api-reference/tracking/sessions/create-session-v-1)
  endpoint with the device ID and optional termination settings.

## Making a session public

You can make a session public from the
[sessions dashboard](https://chrt.com/tracking/sessions), from the session
detail page, or by calling the
[update session](https://docs.chrt.com/api-reference/api-reference/tracking/sessions/update-v-1)
endpoint and setting the visibility field. Public sessions are reachable
by anyone with the URL — no chrt account required.

> **Warning**
>
> Once you make a session public, you cannot make it private again. Your
> only options are to terminate the session (recording stops, the public
> URL keeps history) or delete the session entirely (history goes away
> too).

## Deleting a session

You can delete a session from the
[sessions dashboard](https://chrt.com/tracking/sessions) or from the
session detail page. A public API endpoint for deletion is not currently
documented — contact [trackers@chrt.com](mailto:trackers@chrt.com) if you
need programmatic deletion.

## How to know it worked

* A successful **register device** call returns the new device document
  with `_id`, MAC address, and registration timestamp.
* A successful **create session** call returns the session with `_id`,
  device reference, and termination settings.
* The first telemetry ping can take **up to about 15 minutes** to appear
  via the data-points endpoints after a session starts.

## Related guides

* [Standalone trackers](/trackers/standalone) — the full UI flow these
  endpoints back.
* [Integrations](/trackers/integrations) — Tive sync endpoints and the
  programmatic shipment-level model.
* [Sharing](/trackers/sharing) — give a connected org access to a
  session (UI flow; the API equivalent is the session update endpoint).
* [Tracking concepts](/docs/concepts/tracking) — devices, sessions, and
  pings in detail.
* [API reference](https://docs.chrt.com/api-reference) — full schemas
  and authentication.