Event types
Understand every signal your devices generate. Blecon Network produces structured events whenever devices report positions, connect, send data, or change state — giving you a rich, real-time stream of information to power your applications and integrations.
Network events
Network events are generated by the platform when it processes device signals.
| Event type | Description |
|---|---|
network.device_spotted |
Device detected by a hotspot |
network.device_position |
Device position calculated by the positioning engine |
network.device_first_seen |
Device detected for the first time after registration |
network.device_registered |
Device registered to a network |
network.device_deregistered |
Device removed from a network |
network.response_received |
Webhook response delivered back to a device |
network.request_failed |
Device request failed at the protocol level |
network.routing_failed |
No matching route found for a device request |
Device events
Device events originate from device-initiated communication.
| Event type | Description |
|---|---|
device.request.<namespace>.<method> |
Two-way device request (device expects a response) |
device.message.<namespace>.<method> |
One-way device message (fire-and-forget) |
device.advertising_data |
Raw BLE advertising or status data from a device |
device.request_failed |
Device request processing failed |
The <namespace> and <method> parts are defined by the device's firmware. For example, a device sending sensor data might generate device.message.sensor.reading.
Config events
Config events are generated when resources are created, updated, or deleted via the API.
| Event type | Description |
|---|---|
config.created |
A resource was created |
config.updated |
A resource was updated |
config.deleted |
A resource was deleted |
Event format
Events follow the CloudEvents 1.0 specification:
{
"type": "network.device_position",
"source": "blecon",
"id": "a1b2c3d4-...",
"time": "2026-01-15T10:30:45.123456",
"data": { ... }
}
| Field | Description |
|---|---|
type |
The event type from the tables above |
source |
Always "blecon" |
id |
Unique event identifier (UUID) |
time |
ISO 8601 timestamp (UTC) |
data |
Event-specific payload |
Webhook delivery
Events are delivered to webhook endpoints in batches — a single HTTP POST may contain an array of CloudEvent objects. The system batches up to 50 events per request, with a maximum delay of 1 second.
Related pages
- Data routing
- Event types reference (full payload details)