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

# Authentication

> Learn how requests to the preezie API are authenticated.

Authentication depends on the API feature you are using and the
[@preezie/widget-sdk](https://www.npmjs.com/package/@preezie/widget-sdk).
Use the SDK with your API key to obtain the short-lived operation token, then
include that token in requests to the Core Intent API. Contact your preezie Customer Success Manager to obtain your API key. The key can be rotated when needed.

## Core Intent API

Core Intent requests require both of the following headers:

| Header          | Value                          |
| --------------- | ------------------------------ |
| `Tenantid`      | Your preezie tenant identifier |
| `Authorization` | `Bearer <operation-token>`     |

The operation token returned by the SDK is a short-lived HS256 JWT. Its
`tenantId` claim must exactly match the `Tenantid` request header.

```http theme={null}
Tenantid: tenant-123
Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...
```

<Warning>
  Keep your API key secure and never expose it in public repositories, logs, or
  support messages. Use the SDK to obtain operation tokens rather than minting
  them directly.
</Warning>

Missing, expired, incorrectly signed, or tenant-mismatched tokens return `401 Unauthorized`.

## FAQs and Highlights

FAQ and Highlights requests require only your tenant identifier:

```http theme={null}
Tenantid: tenant-123
```

The tenant identifier selects the catalogue containing the requested product. Send it with every request to `GET /api/faqs/{productId}` and `GET /api/highlights/{productId}`.

## Next step

After obtaining credentials, follow the [Quickstart](/getting-started/quickstart) to make your first request.