1Configuring Nest Operations

To use the Nest connector, add the <nest.init> and <nest.getAccessToken> elements in your configuration before calling any Nest operation.

Nest connector uses Web-based Authorization.

<nest.init>
    <apiUrl>{$ctx:apiUrl}</apiUrl>
</nest.init>

Properties

• apiUrl              : The firebase url of the nest client. (E.g: https://firebase-apiserver01-tah01-iad01.dapi.production.nest.com:9553)
• clientId          : Identification for a control of Nest API.
• clientSecret : Client secret of Nest API.
• code                  : Authorization code to get the access token.

<nest.getAccessToken>
    <clientId>{$ctx:clientId}</clientId>
    <clientSecret>{$ctx:clientSecret}</clientSecret>
    <code>{$ctx:code}</code>
</nest.getAccessToken>

Properties

• apiUrl              : The firebase url of the nest client. (E.g: https://firebase-apiserver01-tah01-iad01.dapi.production.nest.com:9553 )
• clientId          : Identification for a control of Nest API.
• clientSecret : Client secret of Nest API.
• code                  : Authorization code to get the access token.

Additional Information

 Ensure that the following Axis2 configurations are added and enabled in the <ESB_HOME>\repository\conf\axis2\axis2.xml file.

Required message formatters

<messageFormatter contentType="text/html" class="org.wso2.carbon.relay.ExpandingMessageFormatter"/>

Required message builders

<messageBuilder contentType="text/html" class="org.wso2.carbon.relay.BinaryRelayBuilder"/>

Now you have connected to Nest, use the information in the following resources to perform the operations with the connector. After you have completed the configurations, go through Testing the Nest Integration to test those operations.