2.30、Set Third-Party Push Configuration

Set Third-Party Push Configuration

POSTProduction: https://open.eye4cloud.com/{{open_id}}/open/v1/device/setThirdPartyPushConfigParams
Request Data
Field Name Required Type Description
device_id Yes string Device ID
timestamp Yes int64 Timestamp in seconds
nonce Yes string Random string, 8-20 characters
sign Yes string See "Sign Generation Examples" for the implementation details
password No string Device password; if omitted, the password registered for the device on the Open Platform is used
data No string Device DATA; an empty string can be passed
imei No string Device IMEI; an empty string can be passed
heartbeatTime Yes int Heartbeat interval (seconds)
heartbeatServer No string Heartbeat Server URL
alarmPushMainServer Yes string Primary push server URL
alarmPushSubServer Yes string Secondary push server URL
alarmPushVideo No int Whether to push alarm recordings (defaults to 0, do not push, when omitted): 0=do not push, 1=push
CURL Request Example
CURL
curl 'https://open.eye4cloud.com/{{open_id}}/open/v1/device/setThirdPartyPushConfigParams' \
  -H 'Content-Type: application/json' \
  --data-raw '{
    "device_id": "xxxx",
    "timestamp": 1758867195,
    "nonce": "",
    "sign": "",
    "password": "",
    "heartbeatTime":180,
    "heartbeatServer":"",
    "alarmPushMainServer":"xxxx",
    "alarmPushSubServer":"xxxx",
    "alarmPushVideo":1
}'
Response Data
Field Name Type Description
error_code int Status code: 0 indicates success; other values indicate an error
error_message string Error message; success indicates a normal response
data object {}
data.resp int Response: 1 means execution succeeded; 2 means execution failed

Example:

JSON
{
    "error_code": 0,
    "error_message": "success",
    "error_tips": "",
    "data": {
            "resp": 1
    }
}