Bulk recording uptime
Uptime for many recordings in a single request.
Returns uptime for multiple recordings in one call. Use this in place of repeatedly calling GET /recording/:id/uptime.
Date format: uptime endpoints take date-only
YYYY-MM-DDforstartandend. Full ISO 8601 timestamps are rejected.
Body parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
start | string (YYYY-MM-DD) | yes | Inclusive start date |
end | string (YYYY-MM-DD) | yes | Inclusive end date |
recids | string[] | no | List of recording IDs to query. Omit to query all recordings you have access to. |
Example request
POST https://api.auravisionlabs.com/v1/recording/uptimes
Authorization: Bearer <your_token>
Content-Type: application/json
{
"recids": ["64a1b2c3d4e5f6a7b8c9d0e4", "64a1b2c3d4e5f6a7b8c9d0e5"],
"start": "2024-04-01",
"end": "2024-04-07"
}
Example response
Returns an array — one object per recording — with the same shape as the single-recording response:
[
{
"recording": {
"id": "64a1b2c3d4e5f6a7b8c9d0e4",
"name": "Entrance Camera",
"organisation": "64a1b2c3d4e5f6a7b8c9d0e2",
"cameraServer": "64a1b2c3d4e5f6a7b8c9d0e7",
"location": "64a1b2c3d4e5f6a7b8c9d0e3",
"useUploadingSchedule": false,
"timezone": "Europe/London"
},
"uptime": [
{
"index": "2024-04-01 10:00",
"withinSchedule": true,
"segmentsExpected": 4,
"segmentsReceived": 4,
"avgUptimeOnSegment": 0.98,
"pcSegmentsRecieved": 1.0,
"overallUptime": 0.98
}
]
},
{
"recording": {
"id": "64a1b2c3d4e5f6a7b8c9d0e5",
"name": "Back Aisle Camera",
"organisation": "64a1b2c3d4e5f6a7b8c9d0e2",
"cameraServer": "64a1b2c3d4e5f6a7b8c9d0e7",
"location": "64a1b2c3d4e5f6a7b8c9d0e3",
"useUploadingSchedule": true,
"timezone": "Europe/London"
},
"uptime": [
{
"index": "2024-04-01 10:00",
"withinSchedule": true,
"segmentsExpected": 4,
"segmentsReceived": 3,
"avgUptimeOnSegment": 0.91,
"pcSegmentsRecieved": 0.75,
"overallUptime": 0.68
}
]
}
]
Related
- Get recording uptime — single recording
- Historic uptime (Metrics API)
- Real-time status