# API Tokens
Terrakube has two kinds of API tokens: user and team. Each token type has a different access level and creation process, which are explained below.
API tokens are only shown once when you create them, and then they are hidden. You have to make a new token if you lose the old one.
### User API Tokens
API tokens may belong directly to a user. User tokens inherit permissions from the user they are associated with.
User API tokens can be generated inside the **User Settings**.
Click the **Generate and API token** button
Add some small description to the token and the duration
The new token will be showed and you can copy it to star calling the Terrakube API using Postman or some other tool.
#### Delete API Tokens
To delete an API token, navigate to the list of tokens, click the **Delete** button next to the token you wish to remove, and confirm the deletion.
### Team API Tokens
API tokens may belong to a specific team. Team API tokens allow access Terrakube, without being tied to any specific user.
{% hint style="warning" %}
A team token can only be generated if you are member of the specified team.
{% endhint %}
To manage the API token for a team, go to **Settings > Teams > Edit button on the desired team**.
Click the **Create a Team Token** button in the Team API Tokens section.
Add the token description and duration and click the **Generate token** button
The new token will be showed and you can copy it to star calling the Terrakube API using Postman or some other tool.
#### Delete Team API Tokens
To delete an API token, navigate to the list of tokens, click the **Delete** button next to the token you wish to remove, and confirm the deletion.
---
# 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.terrakube.io/user-guide/organizations/api-tokens.md?ask=
```
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.
