algorithm.package.check (Validate algorithm)
algorithm.package.check: Validate algorithm
algorithm.package.check · device scope · permission Config
What it does
Validates an on-device algorithm package. Input: param, ref, type. Returns result. 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 basic configuration permission. A bound sub-user does not. A sub-account needs Config. See Permission codes. Shared devices must satisfy one alias in the capability row share_auth_code (for example Config,config). A timeout does not mean the operation did not execute.
Request parameters
| Name | Type | Required | Description |
|---|---|---|---|
token | String | yes | Administrator, sub-user, or sub-account accessToken |
deviceId | String | yes | Device serial number |
productId | String | no | Optional. If sent and it does not match the device model → DV2009 |
serviceId | String | yes | algorithm.package.check |
inputData | Object | yes | See table below |
| Name | Description | Type | Required | Values |
|---|---|---|---|---|
param | Algorithm parameters. | text | yes | String |
ref | Enable reference. | text | yes | String |
type | Algorithm package type. | enum | yes | 1 human; 2 vehicle; 4 pet; 8 parcel; 16 human region intrusion; 17 vehicle region intrusion; 18 person line-crossing detection; 19 vehicle line-crossing detection; 20 video occlusion; 21 no-person detection; 22 gesture call detection |
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",
"serviceId": "algorithm.package.check",
"inputData": {
"param": "",
"ref": "ref-1",
"type": "1"
}
}
}
Response data fields
Output is in result.data.outputData.
| Name | Description | Type | Required | Values |
|---|---|---|---|---|
result | Validation result. | enum | no | 0 sufficient resources, passed; 1 insufficient compute; 2 insufficient CPU; 3 insufficient memory; 4 insufficient flash; 5 firmware upgrade required; 6 model upgrade required; 7 algorithm conflict; 8 algorithm downloading |
Response example
{
"id": "d5c287b4-5b2f-4f03-baf5-8032c5c354af",
"result": {
"code": "0",
"msg": "Operation is successful",
"data": {
"outputData": {
"result": "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.
