Daikin Airzone - Programmatic Interface

API Integration Manual for Daikin DKN Cloud Wi-Fi Adaptor
7
In this screenshot, the name of the third party application would be visible where the EXAMPLE text
is set. This same is the name provided on the registration process.
Step 3. Once the user authorizes the third party service, the web page will redirect the user-agent
to the application redirect URI specified in the first request, along with an authorization code. This
redirect URI must match one of the valid redirect URLs specified during the client registration. The
authorization code is a temporary code that the client will exchange for an access token. It will be
passed in querystring format. The redirect would look something like this (assuming the application
redirect URL is "example.com"):
https://example.com/?code=hLRlrpTIRUz96crm9PmH5PafXbE4JOAV
At this point, the application has a valid authorization code and can request an Access token. The
remaining requests involved will be explained after describing the programmatic interface access,
since they are the same for both flows.
2.3.2 Programmatic Interface
This interface basically performs the actions described above (Login and Authorize), but without the
need of a browser; only through HTTPS requests. This method is suited for the integration in home
automated systems/BMS. We will describe the structure and format of each of the requests.
Step 1 and 2. Login:
- REQUEST:
- POST https://www.dkncloudna.com/api/v1/auth/login/dknUsa
- HEADERS:
o Accept: application/json
o Content-Type: application/json
- BODY: JSON body parameters:
o email: (String) user email
o password: (String) user password
- EXAMPLE:
curl --location --request POST "https://www.dkncloudna.com/api/v1/auth/login/dknUsa" \
--header "Accept: application/json" \
--header "Content-Type: application/json" \
--data "{\"email\": \"user@email.com\", \"password\": \"examplePassword\"}"
- RESPONSE: This returns a JSON object, where we only are interested in only one of its properties:
token.
Example response:
{
…
"token": "R7k6xX3HsHH1LIPYrCV5SbtYNH7rzFlb…",
…
}
The value of this field is needed for the next request. It acts as an authentication token for the DKN
Cloud NA environment, identifying the request in behalf of the user.
Step 3. Authorization of the third party service: