Discover
Read health, inventory, topology, packets, decoded sensors, and incremental event streams.
GET /v1/diagnostics/eventsDeveloper platform
Build on the live
BliqMesh data path.
Read normalized BLE observations, manage fleet configuration, deploy decoder packs, and connect BliqMesh to your own applications without rebuilding the radio network.
local-api / v1
GET /v1/diagnostics/events?after_id=1842&limit=200
Authorization: Bearer ••••••••
200 OK
{
"events": [{
"id": 1843,
"bleAddress": "AA:BB:CC:DD:EE:FF",
"companyId": 76,
"rssi": -61,
"relayEui64": "880f62fffe37500b"
}]
}
V1.15 stabilizationLoopback REST API · MQTT observations · desired/reported configurationField previewAndroid tablet QA shell · secure QR pairing and live gateway access in development
Quick start
One contract. Several ways in.
Desktop tools use the authenticated loopback API. Enterprise applications consume MQTT through a customer-controlled broker. Mobile apps use a secured application gateway or individually authenticated MQTT identity—never a copied desktop token.
Configure
Get or replace portable modes, rules, storage, MQTT, and decoder settings with no-op detection.
GET /v1/developer/configIntegrate
Subscribe to normalized observations and reconcile retained desired/reported state.
bliqmesh/v1/…Observations
Read once or follow live.
Poll events with the last received id as after_id. This prevents duplicate application work while preserving observation provenance: every event identifies the BliqRelay that heard it.
GET http://127.0.0.1:8787/v1/diagnostics/events?after_id=0&limit=200 Authorization: Bearer $BLIQMESH_TOKEN
Portable configuration
Configure a site. Carry it forward.
The developer configuration document covers operating mode, BLE rules, storage policy, MQTT, and decoder packs. Compare the returned document before writing: unchanged configuration must remain a no-op, avoiding needless device config versions.
GET /v1/developer/config PUT /v1/ble/mode PUT /v1/storage/config PUT /v1/mqtt/config POST /v1/decoders/activate
MQTT
Live data and fleet intent.
bliqmesh/v1/gateways/{anchorId}/application/observationsNormalized application eventsbliqmesh/v1/links/{linkId}/desired/configRetained, signed desired statebliqmesh/v1/links/{linkId}/reported/configApplied version and statusDesired state uses a monotonic sequence and HMAC-SHA256 verification. Use QoS 1 and broker ACLs that restrict every identity to its required site and direction.
Security boundary
Local means local.
The desktop bearer credential stays in the operating-system credential store and the service binds to loopback. Do not copy that token into a mobile app, browser bundle, repository, log, or support file. Remote clients belong behind TLS, unique identities, least-privilege ACLs, rate limits, and audit logging.
Reference clients
Start in your own stack.
The repository developer kit includes runnable examples, an OpenAPI contract, MQTT guidance, and security requirements under src/v1/developer.
Installer tablet
Walk the site. Keep the evidence with you.
The Android tablet QA shell previews site, BliqSensor, network, and installation-audit views. Production mobile access will scan a short-lived, single-use QR pairing request, exchange it for a device-bound credential, and connect through an authenticated gateway. The desktop loopback token is never embedded in the app or QR code.
Delivery roadmap
Talk to sensors—with explicit trust.
V1.15 is the mandatory end-to-end stabilization release before V1.2 begins. The first BliqSensor currently uses the working BLE observation compatibility path. Reliable native delivery is in development: a sleepy BliqSensor hands a high-priority message to a friend-capable relay or hub, receives custody acknowledgement, and returns to sleep while custody advances hop by hop. General commands remain a V2 feature with authentication, authorization, replay protection, correlation IDs, bounded payloads, timeouts, and auditable results.
Build with BliqMesh