Introduction
This document is intended to provide an overview of all the features of ELOCK2 API and how you can best use them. It is oriented around the nine main functions that ELOCK2 offers
Getting Started
To use the ELOCK2 API in production, the given BASE URL must be verified with the user-specific API KEY.
Headers:
Authorization:BasicAuth
Content-type:application/json
Parameters and variables in 'Headers' must be applied every time a request is made.
STEP 1: --> 1.1.7 Register
In this step, a sessionId is generated using the individual name and your individual API key.The appName and sessionName must be assigned. (the naming must be assigned by you)
SAMPLE Register:
INPUT (JSON)
{"appName": "Test Session""sessionName": "Building1","apiKey": "3ab77311-0d4b-461e-91d7-91f8fc16378d"}
OUTPUT (JSON)
{"errormessage": "","sessionId": "62b2216c-7eed-410c-869c-693a45ea7d82","errorcode": 0 }
STEP 2: --> 1.1.4 GetSystems
In this step, we send the "sessionId" value we received in response in the previous step to the relevant address in the request and list the systems that match the "apiKey" value.
SAMPLE GetSystems:
INPUT (JSON)
{"sessionId": "62b2216c-7eed-410c-869c-693a45ea7d82"}
OUTPUT (JSON)
{"result": [
{
"nr": 1,
"name": "Test-System"
},
{
"nr": 2,
"name": "Company System"
}
],
"errormessage": "","errorcode": 0}
STEP 3: --> 1.1.6 LoginSystem
In this step, we can make a request with the "systemId" value and "sessionId" value and userId (Default userId=0 --> Administrator) and password (Default password --> 0000) must be sent to login.
SAMPLE LoginSystem:
INPUT (JSON)
{"sessionId": "62b2216c-7eed-410c-869c-693a45ea7d82","systemId": 1,"userId": 0,"password": "0000"}
OUTPUT (JSON)
{"result": "ok","errormessage": "","systemName": "Test-System","errorcode": 0}
After this step, you are logged into the system. You can use other methods of ELOCK2 API
