API   ->   Token


Token is the credential information that needs to be passed when calling all APIs. If you want to call the API, you need to carry the application information and user information to the specified end point to apply for a token. This means that one token corresponds to one application information and one user information. If you want to use the identity of several different users to call the API, you need to apply for a token for each user.

Token is the first step for the APIs.




http method: GET/POST

Developers need to cache x-auth-token for subsequent interface calls (note: this interface cannot be called frequently, otherwise it will be intercepted frequently). When the x-auth-token is invalid or expired, it needs to be re-acquired. There is no guarantee that the token will continue to be valid during the validity period. Developers should implement the logic for re-acquiring access_token when it expires. x-auth-token reserves at least 256 bytes of storage space.

Return example

		"systemDesc":"CubeDrive: application builder",
		"name":"John Doe",
	"x-auth-token": "32997522-0c9f-4336-80fb-fef717e28248"

Use token

After obtaining the token, user can use the API provided by the platform. When calling the API, user only need to add the Authorization request header (Headers) as shown below.

X-Auth-Token: {{xAuthToken}}
please replace {{xAuthToken}} with x-auth-token value.

User can also pass taken as url parameter:


Validate token

The user can query whether the x-auth-token is valid through this interface.

If it works, the return result as following.