# Server Token

You can use this token type to access a limited set of Whisk API services that do not necessarily require a user context to read, modify, and write data. You can acquire a server token by sending us a request from Whisk Studio. For more information, see [Obtain an API key](broken://pages/-MSEdUHf1ZUXXhVzolMb). A server token is valid for an infinite time but you can ask us to revoke and reissue it if needed. 

To use this token in your request, include it in the `Authorization` header as type `Token`as shown below:

```bash
curl -X GET "https://api.whisk.com/recipe/v2/get?id=9773cb7eca5d11e7ae7e42010a9a0035" \
    -H "accept: application/json" \
    -H "Authorization: Token <Server-Token>"
```

{% hint style="danger" %}
A server token is considered sensitive. It should be stored securely and used only from servers and not client devices.
{% endhint %}


---

# 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/server-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.