Production: https://open.eye4cloud.com/{{open_id}}/open/v1/device/getP2pInfo| Field Name | Type | Required | Description |
|---|---|---|---|
| device_id | string | Yes | Unique device ID (IMEI can also be used) |
| timestamp | int64 | Yes | Timestamp in seconds |
| nonce | string | Yes | Random string, 8-20 characters |
| sign | string | Yes | See "Sign Generation Examples" for the implementation details The data field when generating sign |
| imei | string | No | Device IMEI; an empty string can be passed |
| data | string | No | Custom data; an empty string can be passed |
| password | string | Yes | Device password |
{
"device_id": "xxx",
"timestamp": 1755685731,
"nonce": "dask43hfad",
"sign": "xxxxxxx",
"password": ""
}
curl 'https://open.eye4cloud.com/xxxxx/open/v1/device/getP2pInfo' \
-H 'Content-Type: application/json' \
--data-raw '{
"device_id": "xxx",
"timestamp": 1757472185,
"nonce": "",
"sign": "",
"password": ""
}'
| 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.p2pid | string | Device P2P ID |
| data.initstring | string | P2P Encrypted String |
| data.type | int | Type (0=self-developed, 1=Shangyun) |
| data.vpType | int | Used for app connections |
Example:
{
"error_code": 0,
"error_message": "success",
"error_tips": "",
"data": {
"p2pid": "xxxx",
"initstring": "skadjh123",
"type": 0
"vpType":0
}
}