Documentation

Owner: The entity who will be utilizing the integration to control the system.
Developer: The entity who will be performing the integration with the Open API. For development purposes, may be the same entity as the owner.

1) The owner must download the Daikin One Home App or Amana Home App and create an account. Then they will need to follow app instructions to add thermostats.

2) The owner must request the Integrator Token by navigating to “cloud services” -> “home integration” -> “get integration token”. The owner must agree to the Integration Token Terms. They will be asked to enter their password to finalize the request. They must follow the instruction on the screen.

3) The developer will need an API Key to begin development. The developer must download the same homeowner app as the owner and create an account and enable the developer menu.

How to enable the developer menu:
iOS: Go to the Settings app -> Navigate to the Daikin One Home or Amana Home App and switch on the developer menu option.
Android: Within the Home App, navigate to "cloud services" -> "home integration" and click on the page description 5 times to enable the developer menu

Once enabled, you will be able to navigate to "cloud services" -> "home integration" -> "developer". Upon entering the developer option, you must agree to the Daikin B2B Terms and Daikin One Open API License Terms. Enter the name of the application being integrated with the Daikin One Open API and submit the request. Follow the instructions on the screen.

** The API Key and Integrator Token should be kept secure.

• Only TLSv1.2 and newer secure connections are supported.
• Base URI:

  
  
  
  
  
  https://integrator-api.daikinskyport.com
  
  
  
  
  
  
  
  
  
  
  

• Requests are made with HTTP GET or PUT methods. HTTP GET is used for requesting thermostat information, and HTTP PUT is used for updating thermostat information.
• Request headers must specify JSON encoding for content type header and the API key.

  
  
  
  
  
  Content-Type: application/json 
  
  
  
  
  x-api-key: $INTEGRATOR_API_KEY
  
  
  
  
  
  
  
  
  
  
  
  
  

• Request headers must specify authorization header with the exception of using POST /v1/token.

  
  
  
  
  
  Authorization: Bearer $ACCESS_TOKEN
  
  
  
  
  
  
  
  
  
  
  
  
  

Authentication Token

{



    email: "string",




    integratorToken: "string"



}

{



    accessToken: "string",




    accessTokenExpiresIn: number,



    tokenType: "Bearer"



}

Prior to using the Integrator Cloud API, an end user must provide their email and integratorToken to request the accessToken.

*email is case sensitive

Get Thermostat List

[

    {

        locationName: "string",

        devices: [

            {

                id: "string",

                name: "string",

                model: "string",

                firmwareVersion: "string"

            }

        ]

    }

]

{

    equipmentStatus: 0,

    mode: 0,

    modeLimit: 1,

    modeEmHeatAvailable: 0,

    fan: 0,

    fanCirculate: 1,

    fanCirculateSpeed: 1,

    heatSetpoint: 20.5,

    coolSetpoint: 23.5,

    setpointDelta: 2,

    setpointMinimum: 10.0,

    setpointMaximum: 32.3,

    tempIndoor: 21.5,

    humIndoor: 50,

    tempOutdoor: 20.5,

    humOutdoor: 50,

    scheduleEnabled: false,

    geofencingEnabled: false

}

Update Thermostat Mode – Setpoint Settings

{

    mode: 0,

    heatSetpoint: 20.5,

    coolSetpoint: 23.5

}

{

    message: "string"

}

{

    scheduleEnabled: false

}

{

     message: "string"

}

{

    fanCirculate: 2,

    fanCirculateSpeed: 0

}

{

     message: "string"

}

HTTP response codes represent success or failuer of the operation. Status field in the response body contains additional request or response status information.

{



    messages: "string"



}












                            

Following properties are used in data exchange between third-party integrator applications and thermostats. Data types and validation is strictly enforced.