> For the complete documentation index, see [llms.txt](https://guides.dojah.io/dashboard-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guides.dojah.io/dashboard-guide/integrations/developers/api-tokens.md).
# API Tokens
API Tokens are an alternative authentication method to the main production keys. Where your production keys authenticate all requests from your account broadly, API tokens let you create named, scoped credentials tied to a specific app. This is useful when you have multiple integrations and want granular control over which credential authenticates which integration or when you want to issue credentials to third-party partners or contractors without sharing your master keys.
***
#### Creating a token
Click **Create Token**. Fill in two fields:
**Token name** **–** A descriptive label that identifies what this token is used for, for example, "mobile app – production" or "partner integration – vendor". Use names that make it immediately clear which integration or team member this token belongs to, so you can manage and revoke tokens cleanly.
**Select app** **–** Choose which of your configured apps this token is associated with. The token will authenticate requests attributed to that app.
Click **Create Token** to generate it. Copy the token value immediately when it is first shown, for security reasons; the full token value is only displayed once at creation. After that, only the masked version is visible.
***
#### Managing tokens
Rotate tokens on a regular schedule or immediately if you suspect a token has been exposed. To rotate a token, delete the existing one and create a new one. Update any integration using the old token before deleting it to avoid service interruption.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## 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, and the optional `goal` query parameter:
```
GET https://guides.dojah.io/dashboard-guide/integrations/developers/api-tokens.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.