Initialization
Encedo HEM needs to be initialized before it's usable. This process is called Personalization and these two API endpoints are dedicated for this operation.
These two endpoints are wide open and do not need any authorization data. After the successful personalization of the device, future calls will raise Error 406.
The format of the initialization data is described in "General information".
Personalization
Phase 1 - challenge
Get challenge data
GET
https://my.ence.do/api/auth/init
Get initial data (challenge) as the first step in the personalization process.
Response data for successful operation
Name | Type | Description |
---|---|---|
| String | EncedoID, public key of the instance |
| String | Expire timestamp |
| String | Attestation data |
| String | Token id |
| String | Session public key |
Phase 2 - response
Upload initial configuration
POST
https://my.ence.do/api/auth/init
Upload a well formated initial configuration signed by user passphrase.
Headers
Name | Type | Description |
---|---|---|
Content-Type* | String | application/json |
Request Body
Name | Type | Description |
---|---|---|
init* | String | Initialization structure |
Response data for successful operation
Name | Type | Description |
---|---|---|
| String | Attestation data |
| String | Instance unique ID |
| String | JWT access token (refered as JWT_TOKEN) |
Log entries (directly and indirectly as indicated)
Event | Result | Source |
---|---|---|
LOG_TYPE_DEVICE_INITED | LOG_RESULT_OK | 200 |
LOG_TYPE_STARTUP | LOG_RESULT_OK | On every powerup as second log entry (the first is |
Last updated