> ## Documentation Index
> Fetch the complete documentation index at: https://integration.delogue.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Authentication

> Authenticate Delogue API requests with a personal API key.

All Delogue API requests are authenticated with a personal **API key**, sent in the
`X-Auth-Token` header. You generate the key yourself from your Delogue profile — there is
no separate developer portal or client-secret exchange.

## Create an API key

Access the Delogue beta environment by navigating to
[beta.my.delogue.com](https://beta.my.delogue.com).

Once logged in, click on your **user icon**, and then select **Personal settings**.

<Frame caption="User menu → Personal settings">
  <img src="https://mintcdn.com/deloguecom/ws1tL8x1Vm6Yr8LD/images/authentication/step-01-personal-settings-menu.png?fit=max&auto=format&n=ws1tL8x1Vm6Yr8LD&q=85&s=d6d0bbd62b99a95b39b15e85f9be39e1" alt="Delogue user menu with the Personal settings option" width="633" height="262" data-path="images/authentication/step-01-personal-settings-menu.png" />
</Frame>

<Steps>
  <Step title="Open the Integrations section">
    In Personal settings, open the **Integrations** tab — this is where your personal API
    keys are listed and created.

    <Frame caption="Personal settings → Integrations">
      <img src="https://mintcdn.com/deloguecom/ws1tL8x1Vm6Yr8LD/images/authentication/step-02-integrations.png?fit=max&auto=format&n=ws1tL8x1Vm6Yr8LD&q=85&s=7ae181f01e19b1b93daf57b2f873604f" alt="The Integrations tab in Personal settings" width="650" height="598" data-path="images/authentication/step-02-integrations.png" />
    </Frame>
  </Step>

  <Step title="Create the key">
    Click **Create API key** and give it a clear, descriptive name (for example, the
    integration or script that will use it), then confirm.

    <Frame caption="Naming a new API key">
      <img src="https://mintcdn.com/deloguecom/ws1tL8x1Vm6Yr8LD/images/authentication/step-03-create-api-key.png?fit=max&auto=format&n=ws1tL8x1Vm6Yr8LD&q=85&s=ab9cb98a4c3d9f00f4453cad38c40d43" alt="The Create New API Key dialog" width="639" height="324" data-path="images/authentication/step-03-create-api-key.png" />
    </Frame>
  </Step>

  <Step title="Copy the token immediately">
    Copy the generated token **right away** and store it somewhere safe. For security
    reasons the full token is shown only once, at creation time — it is never displayed
    again. If you lose it, delete the old key and create a new one.

    <Frame caption="Copy the key now — it is shown only once">
      <img src="https://mintcdn.com/deloguecom/ws1tL8x1Vm6Yr8LD/images/authentication/step-04-api-key-created.png?fit=max&auto=format&n=ws1tL8x1Vm6Yr8LD&q=85&s=ae2de94ada1f2ee9b98250fb89b3184f" alt="The API Key Created dialog with a Copy to Clipboard button" width="635" height="495" data-path="images/authentication/step-04-api-key-created.png" />
    </Frame>
  </Step>
</Steps>

<Note>
  A key inherits the permissions of the user who created it, scoped to that user's
  organisation. Create the key under a user whose access matches what the integration
  needs.
</Note>

<Warning>
  Treat the key like a password. Do not commit it to source control or paste it into
  tickets, screenshots, or public channels. If it is ever exposed, delete the key and
  create a new one.
</Warning>

## Send the key

Send the key in the `X-Auth-Token` header on every request:

| Header         | Value                         |
| -------------- | ----------------------------- |
| `Accept`       | `application/json`            |
| `X-Auth-Token` | `Bearer <paste_your_api_key>` |

The `Bearer ` prefix is optional and case-insensitive — the raw key also works.

```bash theme={"dark"}
curl "https://service.staging.delogue.com/api/styles" \
  -H "Accept: application/json" \
  -H "X-Auth-Token: Bearer YOUR_API_KEY"
```

## When authentication fails

| Status               | Meaning                                                                                    | What to do                                                                             |
| -------------------- | ------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------- |
| **401 Unauthorized** | The key is missing, malformed, or no longer valid.                                         | Check that the `X-Auth-Token` header is present and that the key has not been deleted. |
| **403 Forbidden**    | The key is valid, but the user it belongs to lacks permission for that resource or action. | Use a key created under a user who has the required permission.                        |

See [Errors & responses](/concepts/errors) for the full error envelope.

## Need help?

<CardGroup cols={2}>
  <Card title="Knowledge Base" href="https://knowledge.delogue.com/" icon="book-open">
    Product guides and how-tos for the Delogue platform.
  </Card>

  <Card title="Contact support" href="https://knowledge.delogue.com/how-to-get-support" icon="life-ring">
    How to reach the Delogue support team.
  </Card>
</CardGroup>