Getting Started with U home OpenAPI

Technical Support
Technical Support
  • Updated

Get Started with U Home OpenAPI

Development Workflow

Register at U-tec Community - We look forward to your joining and sharing your idea here and then click on Sign Up.

The U Home OpenAPI integration consists of three parts:

 - OAuth2 Authentication Service for cloud access.

- API Interfaces for device interaction.

- Device Status Updates and Event Push Notifications.

#OAuth2 Authentication Service

OAuth 2.0 is the industry-standard protocol for authorization. OAuth 2.0 focuses on client developer simplicity while providing specific authorization flows for web applications, desktop applications, mobile phones, and living room devices.

 

In the most typical scenario, your service does not get an access token directly: it must first get an authorization code and then exchange that for an access token (and, optionally, a refresh token so that it can request a new access token when the old access token expires). The following figure shows the relationship between the key components of account linking, which are described later in this topic. For an example of how users experience the account linking flow.

 

Authorization URI

https://oauth.u-tec.com/authorize?response_type=code&client_id={Client ID}&client_secret={client Secret}&scope={Scope}&redirect_uri={Redirect URI}&state={state}

Callback Redirect URI

https://{Redirect URI}?authorization_code={code}&state={state}

Access token URI

https://oauth.u-tec.com/token?grant_type=authorization_code&client_id={Client ID}&code={code}

 

Related to

Was this article helpful?

0 out of 1 found this helpful

Have more questions? Submit a request

Comments

0 comments

Please sign in to leave a comment.