# Client Token

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 `Token`as shown below:

```bash
curl "https://api.whisk.com/v2/feed" \
  -H "Accept: application/json" \
  -H "Authorization: Token <Client-Token>"
```


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.whisk.com/api-overview/auth/client-token.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.