Build with Hellotracks - Hellotracks developer docs

Hellotracks has three ways in. They reach the same company data: jobs, routes, people, places, timesheets, forms and reports. Pick the one that fits how you work. All three use the same API key, from More → API & Integrations in the dashboard.

JSON API

Build an integration in code, with one JSON request per action.

REST API

Build tools and automations on plain REST resources.

CLI

Work from a terminal or let an AI agent run things. One install line.

The same task three ways

List today’s jobs for every worker.

curl -X POST https://api.hellotracks.com/api/getjobs \
  --header 'API-Key: YOUR_KEY_ID.YOUR_SECRET' \
  --header 'Content-Type: application/json' \
  -d '{ "data": { "worker": "*" } }'

curl "https://api.hellotracks.com/v1/jobs?date=2026-11-02" \
  --header 'API-Key: YOUR_KEY_ID.YOUR_SECRET'

ht jobs list --date today

Which one fits

	Good for	Looks like
JSON API	Integrations written by developers	`POST /api/getjobs` with a JSON body
REST API	Tools, automations and services over HTTP	`GET /v1/jobs`
CLI	Terminals, scripts, CI and AI agents	`ht jobs list`

Each has things the others don’t yet: the JSON API has dispatch, live locations and GPS tracks; the REST API and the CLI have timesheets, forms, alerts, ETA pages and maps; the CLI adds bulk import, sync and export.

AI agents: read For AI agents. In short: use the CLI. If you can only make HTTP requests, use the REST API.

Help

Questions about any of the three: api@hellotracks.com.

JSON API

REST API

CLI

​The same task three ways

​Which one fits

​Help

The same task three ways

Which one fits

Help