You can embed a client token into native mobile binaries or desktop apps to identify your app. This token is not meant to be a secret identifier because it is embedded in apps. It is a analogue of the Server Token. The only difference is that it is less secure and can be stored on the client-side.
Your application may use a client token when accessing a limited set of resources that are not specific to a user and can be made available to the client device or browser directly.
To use this token in your request, include it in the
Authorization header as type
Tokenas shown below:
curl "https://api.whisk.com/v2/feed" \-H "Accept: application/json" \-H "Authorization: Token <Client-Token>"