Tracker API

Blecon Track is built entirely on the API. Every feature in the Blecon Track dashboard (the map, trails, rules, zone management, alerts) uses these same endpoints. Anything you can do in Blecon Track, 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 Blecon Track.

Base URL

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

All endpoints are scoped to a workspace:

https://api.blecon.net/tracker/api/workspaces/{workspace_id}/...

Authentication

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

You can create and manage API keys directly from the Blecon Track dashboard: open Settings in the sidebar and select API.

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 (with tag, type, zone, status and custom-field filters), query position history, sensor history, timeline, child assets, and association history. Assets support tags and custom fields.
Positions and trails: All tag trails, location statistics, and trail density.
Trips and stops: List trips across the workspace or for one asset, fetch a single trip with its recorded route, list stops, and export the filtered list as CSV. Filter by time, asset, zone, minimum distance and minimum duration, and by the same asset filters as the asset list (kind, type, keyword, team, search, custom fields). Asset filters read each asset as it is now. Trips are of tags by default: pass entity_kind=agent for devices or all for both.
Zones: Create coordinate zones, list/update/delete zones, zone tags, and zone transition history. Network zones are created in Zones → Network Zones and appear in Blecon Track automatically.
Rules: Create, list, update, and delete rules.
Alerts: List alerts (filterable by status, severity, assignee, and the asset filters of the asset list), alert statistics, acknowledge, resolve, and add notes.
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 tag registration via the Blecon Agent.
Hubs: Register and manage hubs, matching the Network page in the Blecon Track dashboard. Requires the Enterprise tier.

Asset times

An asset in an API response carries these times, in ISO 8601 UTC. They have the same names as the columns of the asset list.

Field	What it holds
`last_position_at`	Time of the last confident position. An approximate position does not change it. Zones and rules use this position.
`last_sensor_data_at`	Time of the latest sensor data, such as temperature or battery voltage.
`last_detected_at`	Time of the latest detection of any kind: a position, sensor data, or a detection that gave no position.
`first_detected_at`	Time of the first detection of any kind.
`last_position_hotspot_id`, `last_position_hotspot_name`	The registered Blecon Agent device that detected the asset at its last position. These fields are empty when another type of hotspot reported the position. The asset list fills them in only with `resolve_hotspots=true`; without it, the list gives the hotspot ID alone, for any type of hotspot.

Earlier versions of the API used other names for these fields: position_sample_time, latest_sensor_time, last_position_or_data_at, first_position_or_data_at, last_seen, first_seen, last_hotspot_id and last_hotspot_name. Responses still include the earlier names, with the same values, so existing integrations continue to work. The API reference does not show them, and a later version of the API will remove them. Use the new names in new code. The same applies to labels and tags on an asset: use keywords.

Building on the API

Blecon 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 alert data into your ERP, CMMS, or workflow tools. Acknowledge, assign, and resolve alerts programmatically (see alert lifecycle).
Extend the scanner: use scan sessions to register tags from your own mobile app (see scanner integration).

API keys