1. Connect a registered camera
- Enable CCTV for the organisation and register the camera under its branch.
- Use the camera-specific 64-character lowercase hexadecimal token in
X-Camera-Token. Entry Device credentials are issued separately. - Send JSON over HTTPS to the endpoint below. The existing URL includes
attendance. - Use the CCTV Connector to configure and sync detection, zone rules and delivery settings. For a custom event sender, verify the camera has applied settings and enabled recipients.
POST https://www.entryluma.com/api/v1/attendance/zones.php
Content-Type: application/json
X-Camera-Token: <camera token>
2. Submit a live alert or resolution
Detection runs in the CCTV Connector or camera integration. Submit the event with a 32-character lowercase hexadecimal event_key, a kind of alert or resolution, and occurred_at in Unix epoch seconds. Use a different event key for the resolution. At receipt the timestamp may be up to one hour old or two minutes ahead.
{
"api_version": 1,
"operation": "live_event",
"event_key": "0123456789abcdef0123456789abcdef",
"kind": "alert",
"occurred_at": 1794300000
}
Replace the illustrative ID and timestamp before sending. Optionally include a raw base64 JPEG in image (up to 700,000 encoded characters, with no data URL prefix). The full request is limited to 720,000 bytes. Snapshot delivery depends on portal storage and delivery configuration.
3. Check responses and delivery
- 201 records a new event. It can queue real WhatsApp or email messages for configured recipients.
- 200 with
duplicate: truerecognises an existing event key. For transient failures, retry with the same key and payload while the timestamp remains valid. - 401 indicates an invalid camera credential. 403 indicates CCTV or the camera is disabled.
Test on an authorised camera. Check CCTV activity and notification delivery in the portal to confirm the outcome.
4. Configuration and episode compatibility
Use {"api_version":1,"operation":"configuration"} to read camera configuration and enabled state. A disabled camera can return enabled: false for the read and reject event submissions. The revision-based open and resolve operations remain available for existing episode integrations. Use live_event for the current camera notification workflow.
