record.timelapse.calendar (Get device timelapse album calendar)
record.timelapse.calendar: Get device timelapse album calendar
record.timelapse.calendar · channel scope · permission RecordReplay
What it does
Queries the timelapse album task calendar for this channel. Input num, order (0 ascending, 1 descending), sessionId. Returns count, task (up to 100 items), and session. Each call runs once.
Request URL
POST https://openapi-[DataCenter].easy4ip.com/openapi/v2/device.service.invoke
Minimum permission
The administrator does not need an extra permission on a device they bound. A shared device needs the cloud recording view permission. A bound sub-user does not. A sub-account needs RecordReplay. Omitting channelId on channel-scope capabilities returns DV2007. Mixing device and channel properties in one request returns DV2008. A timeout does not mean the invoke failed.
Request parameters
| Name | Type | Required | Description |
|---|---|---|---|
token | String | yes | Access token for an administrator, sub-user, or sub-account |
deviceId | String | yes | Device serial number |
productId | String | no | Optional. If sent and it does not match the device model → DV2009 |
channelId | String | yes | Channel ID; "0" is common for IPC |
serviceId | String | yes | record.timelapse.calendar |
inputData | Object | yes | See table below |
| Name | Description | Type | Required | Values |
|---|---|---|---|---|
num | Number of entries to query. Range 0–999999, step 1. | int | yes | 0–999999, step 1 |
order | Query order. 0 ascending, 1 descending. | enum | yes | 0 ascending; 1 descending |
sessionId | Query session ID. | text | yes | String |
For common request fields and signing, see Signing conventions and Common request payload.
Request example
{
"id": "d5c287b4-5b2f-4f03-baf5-8032c5c354af",
"system": {
"ver": "1.0",
"appId": "lcdxxxxxxxxx",
"sign": "xjhCQBoJ9hRDsCjyDcHjtDNzRZ3ZJezcawsfWeiaoxU=",
"time": 1706511734,
"nonce": "f5a1ae2d-c09c-4d39-a744-83a5c2c653c2"
},
"params": {
"token": "<yourAccessToken>",
"deviceId": "TESTIPC000012345",
"channelId": "0",
"serviceId": "record.timelapse.calendar",
"inputData": {
"num": 10,
"order": "1",
"sessionId": ""
}
}
}
Response data fields
Output is in result.data.outputData.
| Name | Description | Type | Required | Values |
|---|---|---|---|---|
count | Task count. Range 0–999999, step 1. | int | no | 0–999999, step 1 |
task | Timelapse tasks. Up to 100 items. | array | no | Up to 100 items |
session | Query session ID. | text | no | String |
task.item.id | Timelapse task ID. | text | no | String |
task.item.state | Task state. 0 complete, 1 recording. | enum | no | 0 complete; 1 recording |
task.item.duration | File duration. Range 0–999999, step 1, unit s. | int | no | 0–999999, step 1, unit s |
task.item.sceneName | Scene name. | text | no | String |
task.item.createTime | Task creation time. Format YYYY-MM-DD HH:mm:ss. | text | no | Format YYYY-MM-DD HH:mm:ss |
task.item.path | Timelapse task storage path. | text | no | String |
task.item.fileSize | Generated file size. Range 0–999999, step 1, unit byte. | int | no | 0–999999, step 1, unit byte |
task.item.type | Type. 0 video, 1 image. | enum | no | 0 video; 1 image |
Response example
{
"id": "d5c287b4-5b2f-4f03-baf5-8032c5c354af",
"result": {
"code": "0",
"msg": "Operation is successful",
"data": {
"outputData": {
"count": 1,
"session": "s-1",
"task": [
{
"id": "task-1",
"state": "1",
"duration": 60,
"sceneName": "Entrance",
"createTime": "2026-09-19 08:00:00",
"path": "/mnt/sd/tl",
"fileSize": 1024,
"type": "0"
}
]
}
}
}
}
Error codes
| Code | Meaning | Next step |
|---|---|---|
SN1001 | Signature error | Check sign per Development specification |
TK1002 | Token invalid or expired | Refresh accessToken |
OP1002 | Missing required parameter | Add required fields |
OP1003 | Invalid parameter | Match this page’s parameter table |
OP1009 | Permission denied | Check token and device bind/share grants |
OP1013 | Total call limit exceeded | Reduce call rate |
OP1014 | Daily per-interface limit exceeded | See Interface call limits |
DV1007 | Device offline | Wait until the device is online |
See Return codes · OP/SN/TK for the full catalog.
| Code | Meaning | Next step |
|---|---|---|
DV2003 | Capability not on device | Use device.capability.list |
DV2007 | channelId vs scope mismatch | Required for channel scope; omit for device scope |
DV2008 | Mixed device and channel in one call | Split the request |
DV2009 | productId mismatch | Omit or set actual model id |
DV2011 | No capability permission | See Permission codes |
See Capability errors.
