Authentication APIs


Application developers who want to build App for My Cloud platform must submit a request to My Cloud Admin. Please refer App Registration Process for more details. My Cloud Admin will verify the App request and generates a unique Client ID/Secret for the requested App. The Authentication APIs deal with the identity functionality of My Cloud Home. If you are accessing My Cloud Home from a desktop/web/mobile/service, then you need Authorization Header in all your requests. Bearer token included in the Authorization header identifies the user and his/her permissions to access the content. Following sections explain different operations in authentication and user management. Application must use the {service.auth0.url} url (endpoint url) retrieved in EndpointFetching for making these API calls.

  1. Obtain credentials (Client ID/Secret) for your application.
    You can request credentials for your application. Detailed information on how to become a My Cloud developer and how to register your application can be found here. /distribute

  2. Obtain an access token from My Cloud authentication server.
    Based on the credential received in step #1. apps can request token on behalf of user. Detailed information about the token API request/response can be found here. /discover/authentication

  3. Add access token in all API
    All My Cloud APIs require token in header. Token must be in 'Authorization: Bearer xxx' format.

    For example:

    GET /cloud/sdk/v2/files/8341 HTTP/1.1
    Authorization: Bearer eyJ0eXAiOiJKV1QiLCJhbGciOiJSUzI1NiIsImt

  4. Refresh token, if necessary.
    My cloud access tokens has limited life time and app developer needs to get new token when the existing one expires. App developer can request for refresh token in the signin request by adding offline_access scope. Using refresh token obtained in Step #2, application can request for new token. Detailed information about the token refresh API is described here. /discover/authentication

  5. Get user info
    Application may have to get additional information about the user. For example, name, email, profile picture etc. Detailed information about the user information API is described here. /discover/authentication


  • getUserInfo: Get user information by email or user-id

Have question about this section?