AIRlert POSTs selected HUB messages to your HTTPS endpoint as signed JSON. Your system verifies the request, stores or routes the event, and returns an accepted HTTP status.
user_data.allowed_hub_ids, AIRlert POSTs the event to your endpoint.200 or 202.| Method | POST |
|---|---|
| Content type | application/json; charset=utf-8 |
| Event header | X-Airlert-Event: hub.message.ingested |
| Delivery id | X-Airlert-Delivery-Id |
| User agent | AIRLERT-OPEN-API/1.0 |
Your production endpoint is configured server-side. Example target format: http://mirror.airlert.co.uk/php/your-partner-endpoint
The payload shape is stable. Field names below match the OpenAPI document.
{
"type": "airlert.hub.message.ingested",
"schema_version": "1.0",
"event_id": "airlert-9a8b7c6d5e4f3210abcd1234-a1b2c3d4",
"occurred_at_unix": 1781766000,
"occurred_at": "2026-06-18T06:20:00Z",
"source": "airlert_portal",
"ingest_endpoint": "tttupload.php",
"hub": {
"canonical_hub_id": 42,
"user_data_hub_id": 42,
"hub_name": "Bedroom hub",
"user_id": 3
},
"message": {
"location": "Room 1",
"sensor": "Bed pad",
"raw": "Not Return to Bed",
"presented": "Not Return to Bed",
"user_data_id": 123456
}
}
Authorization: Bearer ... against the token agreed for your endpoint.X-Airlert-Signature when a shared_secret is configured.sha256=<hex>.shared_secret.200 or 202 when accepted.open_api.Use the live OpenAPI JSON for schema validation and generated client/server code.