> For the complete documentation index, see [llms.txt](https://docs.g-iot.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.g-iot.io/platform-user-guide-book/administration/tenant/tenant-api.md).
# Tenant API
## API
The "Tenant API" refers to an API (Application Programming Interface) designed to manage and interact with the resources of a single Tenant.
Create API Tokens
## Steps to Create API-Tokens
1. **Access Administration:**
* Navigate to the cockpit menu, go to "Administration," and select "Tenant."
2. **Open API Section:**
* Click on "API" to open the menu, then click the "Create" icon on the right side of the screen.
3. **Fill in Required Information:**
* **Name:** Enter a required name for the API token.
* **Description:** Add a description to facilitate the organization of the Tenant.
* **Expiration Date (optional):** Set an expiration date if needed.
* **Tenant:** Select the specific Tenant to receive the API call, or choose "All Tenants."
* **Permissions:** Select or deselect permissions such as Read, Write, Create, Delete.
4. **Generate and Save API Token:**
* Click "Next" to generate the API token. The token will be displayed and can be copied.
5. **Click "Save" to complete the process.**
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.g-iot.io/platform-user-guide-book/administration/tenant/tenant-api.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
