# Client Token

## Client Token Authentication

The client token is an identifier that you can embed into native mobile binaries or desktop apps to identify your app. The client token isn't meant to be a secret identifier because it's embedded in apps.

Your application may use a client token when accessing a limited set of resources that are not specific to a user and made available to the client device or browser directly. To do this, include client token in the Authorization header as type Token.

Here’s an example request, using the [Recipe Feed](/master/api/recipe-discovery/recipe-feed.md) endpoint.

```bash
curl "https://graph.whisk.com/v1/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/master/api/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.