---
updatedAt: 2026-10-06T15:32:58.000Z
agentTools:
  projectIndex: https://docs.quable.com/v5-EN/llms.txt
---

# API Tokens

The **API Tokens** page lets you generate and manage your own access tokens to use the Quable PIM API.

<Callout icon="⚠️" theme="warn">
  Important: Quable PIM displays the plain-text token only once, right after it is created. Copy it and store it somewhere safe: you cannot retrieve it once this window is closed.
</Callout>

<Image src="https://files.readme.io/98dffc4fb84845c4bdeae6947ade6381041bd9df8b9a59db25be11d17f0de80b-Capture_decran_2026-04-08_a_14.23.27.png" alt="API token list" align="center" />

***

## Prerequisites

1. Open the **API Tokens** page in Quable PIM.
2. Make sure you have access to token management. Administrators have access by default.

***

## Access levels

Two access levels are available when creating a token:

### Read access (`read`)

Grants limited, read-only access to the Quable PIM API. This token does **not** allow you to add, update or delete content.

Supported HTTP methods: `GET`

### Read/Write access (`read_write`)

Grants full, unrestricted access to the Quable PIM API. This token gives access to all Quable PIM features.

Supported HTTP methods: `GET` `POST` `PUT` `DELETE`

<Callout icon="💡" theme="default">
  Administrators have access to token management by default.
</Callout>

***

## Create a token

1. Click **Create token** on the management page.
2. Fill in the following fields:
   * **Name** (required) — A descriptive name to identify the token, e.g. `My application`.
   * **Access level** (required) — `Read` (`read`) or `Read/Write` (`read_write`).
   * **Expiration** (required) — Choose from: 1 day, 1 week, 1 month, 3 months, 6 months, 1 year, or no expiration.

<Image src="https://files.readme.io/b941b24eec24042fa0989199435ba9bd6e37402ddc2356c0c4aed310d3ba492a-Capture_decran_2026-04-08_a_14.21.22.png" alt="API token creation" align="center" />

3. Click **Create**.
4. **Copy the displayed token immediately.** Once this window is closed, you can no longer view it.

<Image src="https://files.readme.io/38ed2a9a769110c668435aa3837c4b514fc6eab62b0e5d9e404ea08127b9a2c8-Capture_decran_2026-04-08_a_14.22.03.png" alt="Generated API token" align="center" />

***

## Manage your tokens

The list displays all your tokens with the following information:

| Column        | Description                                    |
| ------------- | ---------------------------------------------- |
| Name          | The name you gave the token                    |
| Creation date | The date the token was created                 |
| Access level  | `Read` (`read`) or `Read/Write` (`read_write`) |
| Expiration    | The expiration date, or `Never`                |
| Status        | `Active`, `Expired` or `Revoked`               |

***

## Revoke a token

You can only revoke tokens with the **Active** status.

1. Click the revoke icon on the row of the token you want to revoke.
2. In the confirmation window, type `REVOKE` to confirm.

<Image src="https://files.readme.io/21e226e7a2c466a1e9cb5994bd12131de03bedf94a5d3d0efb575a5d05fa76e0-Capture_decran_2026-04-08_a_14.23.08.png" alt="Revoke a token" align="center" />

3. Click **Revoke**.

<Callout icon="⚠️" theme="warn">
  Revocation is permanent: it immediately invalidates the token, which you cannot reactivate.
</Callout>

***

## Token statuses

| Status      | Description                        |
| ----------- | ---------------------------------- |
| **Active**  | The token is valid: you can use it |
| **Expired** | The expiration date has passed     |
| **Revoked** | The token has been revoked         |

***

## Use a token

Once copied, add the token to the `Authorization` HTTP header of your requests:

```http
Authorization: Bearer your_token
```

The base URL of the Quable PIM API is your Quable PIM URL followed by `/api` (e.g. `https://example.quable.com/api`).

To test it from the interactive API documentation:

1. Open the API documentation and click the **Authorize** button.
2. In the **Value** field, enter `Bearer` followed by your token.
3. Click **Authorize** to activate the session.

<Callout icon="💡" theme="default">
  Don't forget to type the `Bearer` keyword followed by a space before your token.
</Callout>

## Troubleshooting

* If your request fails, check that the `Authorization` header contains `Bearer` followed by a space and the token you copied when it was created.
* If the token is **Expired** or **Revoked**, create a new token: a revoked token cannot be reactivated.
* If an add, update or delete operation fails with a **Read** (`read`) token, use a **Read/Write** (`read_write`) token instead.