> 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.md).

# API tokens

Learn about creating and managing API tokens in the SoftwareOne Marketplace.

The Marketplace Platform uses API tokens to authenticate requests to the [REST API](broken://pages/c48wsZ6OnZim0prmKKFx).

Your API token must be included in the `Authorization` HTTP header with the **Bearer** prefix for authentication. For example, the following request could be used to retrieve a list of buyers:

```http
GET https://api.platform.softwareone.com/public/v1/accounts/buyers
Authorization: Bearer {TOKEN_VALUE}
```

Your API keys have permissions assigned to them, so keep them secure. Do not share your secret API keys in public areas, such as GitHub or client-side code. 

All API requests must be made over HTTPS. Requests sent over HTTP or without authentication will fail.

### API tokens page

The **API tokens** page lets account administrators create, view, edit, delete, enable, and disable API tokens.

To open the page, choose **Settings** > **API tokens** from the main menu.

<div data-with-frame="true"><figure><img src="https://content.gitbook.com/content/Z5DNbniz33mXCZoO62Rm/blobs/kvC0WviWr5LSenWHB5rU/API%20token.png" alt=""><figcaption><p>Use the <strong>API tokens</strong> page to view and manage tokens.</p></figcaption></figure></div>

On the **API tokens** page, you can view details for each token, including the token name, creation date, status, and more.&#x20;

You can also select a token to view detailed information organized across several tabs. These details include the token endpoint and secret, event history, and other token‑specific information. For details, see [View API tokens](/modules-and-features/settings/api-tokens/view-api-tokens.md).

### Related topics

{% content-ref url="/spaces/Z5DNbniz33mXCZoO62Rm/pages/bvXxRDxbNRzUgKnpdYrQ" %}
[Token states](/modules-and-features/settings/api-tokens/token-states.md)
{% endcontent-ref %}

{% content-ref url="/spaces/Z5DNbniz33mXCZoO62Rm/pages/HXRWVPZ8CzAOzNqXOC8H" %}
[Create API token](/modules-and-features/settings/api-tokens/create-api-token.md)
{% endcontent-ref %}

{% content-ref url="/spaces/Z5DNbniz33mXCZoO62Rm/pages/de7yiifdzqU8Ea1qt0ZU" %}
[View API tokens](/modules-and-features/settings/api-tokens/view-api-tokens.md)
{% endcontent-ref %}

{% content-ref url="/spaces/Z5DNbniz33mXCZoO62Rm/pages/VCzRjYa3bzFKDfsm0NV1" %}
[Edit API token](/modules-and-features/settings/api-tokens/edit-api-token.md)
{% endcontent-ref %}

{% content-ref url="/spaces/Z5DNbniz33mXCZoO62Rm/pages/QcTrxA2OKMiaKp1kzKO2" %}
[Copy API token](/modules-and-features/settings/api-tokens/copy-api-token.md)
{% endcontent-ref %}

{% content-ref url="/spaces/Z5DNbniz33mXCZoO62Rm/pages/NBzLiN2ZsiHOMFdvjgGF" %}
[Delete API token](/modules-and-features/settings/api-tokens/delete-api-token.md)
{% endcontent-ref %}

{% content-ref url="/spaces/Z5DNbniz33mXCZoO62Rm/pages/x79WQOZRGuANQ9VsguZZ" %}
[Enable or disable API token](/modules-and-features/settings/api-tokens/enable-or-disable-api-token.md)
{% endcontent-ref %}


---

# 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.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.