Tracker API

Blecon Track is built entirely on the Tracker API. Every feature in the Track UI — the live map, trails, alert rules, zone management, violations — uses these same endpoints. Anything you can do in the Track UI, you can do programmatically via this API.

This means you can build your own tracking applications, dashboards, and automations on top of the same API that powers Track.

Base URL

https://api.blecon.net/tracker/api

All endpoints are scoped to a workspace:

/api/workspaces/{workspace_id}/...

Authentication

The Tracker API uses the same authentication as the Blecon Network API:

Browser sessions — Sign in to Blecon Track to authenticate interactively.
API keys — Programmatic access via API keys. Include the key in the Authorization header.

API reference

The full interactive API reference is available at api.blecon.net/tracker/docs. It covers all endpoints with request/response schemas and lets you try calls directly.

Key resource groups:

Assets — List assets, query position history, sensor history, timeline, child assets, and association history.
Positions and trails — All device trails, location statistics, and trail density.
Zones — Create coordinate zones, list/update/delete zones, zone tags, and zone transition history. Network zones are created in the Blecon Console and appear in Track automatically.
Alert rules — Create, list, update, and delete alert rules.
Violations — List violations (filterable by status), violation statistics by severity.
Webhook channels — Create, list, update, and delete webhook channels for alert notifications.
Members — List workspace members, invite by email, manage roles, remove members.
Scan sessions — Create scan sessions for device registration via the Blecon Agent.

Building on the Tracker API

Track is a reference implementation built on this API. You can use the same endpoints to:

Build custom dashboards — query asset positions, zone occupancy, and trail data for your own UI.
Automate alert management — create and update alert rules programmatically as your operations change.
Integrate with business systems — pull violation data into your ERP, CMMS, or workflow tools.
Extend the scanner — use scan sessions to register devices from your own mobile app (see scanner integration).

Blecon Network API vs Tracker API

	Blecon Network API	Tracker API
Docs	api.blecon.net/docs	api.blecon.net/tracker/docs
Base path	`/v1/accounts/{id}/...`	`/api/workspaces/{id}/...`
Scope	Networks, devices, hotspots, integrations	Assets, zones, alert rules, violations
Purpose	Device management and data routing	Tracking application features

Both APIs use the same authentication. A Blecon Track workspace is linked to a Blecon Network account.