> For the complete documentation index, see [llms.txt](https://docs.platform.softwareone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.platform.softwareone.com/modules-and-features/settings/api-tokens/create-api-token.md).

# Create API token

Create API tokens to access the platform programmatically.

Use API tokens to access the platform programmatically. Account administrators can create and manage tokens directly in the platform.

### Create a new API token

To create a new API token:

1. Go to **Settings** > **API tokens**. 
2. Select **Add**.

<div data-with-frame="true"><figure><img src="https://content.gitbook.com/content/Z5DNbniz33mXCZoO62Rm/blobs/hOGPiaSoVCtT2ht18eV4/image.png" alt=""><figcaption><p>Use the Add API token wizard to add a new token.</p></figcaption></figure></div>

3. Complete the steps in the **Add API token** flow:
   1. **General** – Enter the required token details, then select **Next**:
      1. **Logo** – (Optional) Upload an image or drag your file into the upload area.&#x20;
      2. **Name** – (Required) Enter a name for the token.&#x20;
      3. **Description** – (Optional) Add a description.
   2. **Modules** – Select the modules that the token can access, then select **Next**. Only modules enabled for your account are shown.&#x20;
   3. **Overview** – Review the details, then select **Add**. The token is created, and a summary is displayed.
   4. **Summary** – Select **View details** to open the token details page or select **Close**.&#x20;


---

# 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.platform.softwareone.com/modules-and-features/settings/api-tokens/create-api-token.md?ask=<question>&goal=<user_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.