https://api.sciener.com/v3/lock/initialize
Alert:Call this api after calling APP SDK method to add a lock, lockData must be get from the callback function of Lock initialie method of APP SDK.
This API will initialize the lock in the cloud server,and will generate an admin ekey for the user.
If the lock is successfully added in Sciener APP,it is already initialized, there is no need to request this API. Just request cloud API: Get the lock list of an account to get the lock. You can also get lockId in Sciener APP 's lock basics page (Settings->Basics),as shown in screenshot below:

POST, ContentType:application/x-www-form-urlencoded
xxxxxxxxxxcurl --location -g --request POST 'https://api.sciener.com/v3/lock/initialize' \--data-urlencode 'clientId=4773aa036f7f49c68d876bb4be85c80c' \--data-urlencode 'accessToken=dfd5489d0cee31f0bdfaf59d0d42d71f' \--data-urlencode 'lockAlias=Lock of 1-4-201' \--data-urlencode 'lockData=xxxxxxxxxxxxx' \--data-urlencode 'date=1625025703000'
| Name | Type | Required | Description |
|---|---|---|---|
| clientId | String | Y | client_id from Create application |
| accessToken | String | Y | Access token,refer to: Get access token |
| lockData | String | Y | Lock Data,must be get from the callback function of Lock initialie method of APP SDK |
| lockAlias | String | N | Lock alias |
| groupId | Int | N | group ID,refer to cloud API: Add group |
| nbInitSuccess | Int | N | Is NB-IoT lock inited Successfully? 1-yes, 0-no. Only NB-IoT lock need this parameter. |
| date | Long | Y | Current time (timestamp in millisecond) |
| Parameter | Type | Description |
|---|---|---|
| lockId | Int | Lock ID |
| keyId | Int | Admin ekey id |
xxxxxxxxxx{"lockId": 123132,"keyId": "2342342"}