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.
Last updated
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.
Last updated
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".
GET https://my.ence.do/api/auth/init
Get initial data (challenge) as the first step in the personalization process.
| Name | Type | Description |
|---|---|---|
POST https://my.ence.do/api/auth/init
Upload a well formated initial configuration signed by user passphrase.
| Name | Type | Description |
|---|---|---|
| Name | Type | Description |
|---|---|---|
| Name | Type | Description |
|---|---|---|
| Event | Result | Source |
|---|---|---|
eid
String
EncedoID, public key of the instance
exp
String
Expire timestamp
genuine
String
Attestation data
jti
String
Token id
spk
String
Session public key
Content-Type*
String
application/json
init*
String
Initialization structure
genuine
String
Attestation data
instanceid
String
Instance unique ID
token
String
JWT access token (refered as JWT_TOKEN)
LOG_TYPE_DEVICE_INITED
LOG_RESULT_OK
200
LOG_TYPE_STARTUP
LOG_RESULT_OK
On every powerup as second log entry (the first is LOG_TYPE_KEY_INIT)