# API Tokens

Access to the endpoints documented at api.grax.com and served on every GRAX application is controlled via API tokens, which can be managed from within the related GRAX application. Tokens can be assigned limited feature access, named, and disabled.

## Creating an API Token

Tokens can be managed via the "API Tokens" section on the "Settings" page. Click "New Token" to configure your token permissions and name.

<figure><img src="/files/Hf2cG7R3nWyDBF9Gn7EH" alt="" width="524"><figcaption></figcaption></figure>

<figure><img src="/files/6T8lXw8OtSSrTcK7IrFA" alt="" width="451"><figcaption></figcaption></figure>

Once you've selected the permissions you want the token to have, click "Save" to create it. **The token value will only be shown once after creation.** You must store it in a safe location before leaving the page. If you lose it, you will need to create a new token.

<figure><img src="/files/oRdjCv53KcYv2fCC36pl" alt=""><figcaption></figcaption></figure>

## Deleting an API Token

Tokens can be deleted by clicking the trash can icon in the API Tokens list, shown above. A confirmation window ensures that tokens are not accidentally deleted.

<figure><img src="/files/w9LEigsffqv2uAMs5TcT" alt=""><figcaption></figcaption></figure>

## Using an API Token

Tokens are used for authenticating and authorizing requests to the GRAX application API. The tokens must be passed to the API as part of the Authorization header in every request.

For more information and examples, see the static API documentation at <https://api.grax.com> or the interactive API documentation at `/scalar` on your own GRAX application.


---

# 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://documentation.grax.com/other/permissions-and-access/api-tokens.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.
