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

# Authentication

> Use API keys to call the documented read endpoint from your own stack

## Overview

The **documented** authenticated route is **`GET /v1/projects`**. Use an **API key** from the dashboard so your backend or scripts can pull projects and **published** changelog entries without using the SuprLogs UI.

1. Sign in at [suprlogs.com/app](https://suprlogs.com/app) and open **Settings** → **API Keys**.
2. Create a key, give it a name, and **copy the secret once** — it is shown only at creation.
3. Send the secret on each request:
   * `Authorization: Bearer <your-api-key>`, or
   * `X-API-KEY: <your-api-key>`

## Scope model

Each key is created in a **Personal** or **Organization** context and can be limited to:

* **All projects** in that context, or
* **Selected projects** (e.g. a single project).

**`GET /v1/projects`** only returns projects the key is allowed to see. Wider product APIs (not listed in this reference) may apply the same rules.

## Lifecycle and security

* Create, rename, rotate, revoke, and delete keys in the **dashboard** — not via the documented API.
* Revoked or deleted keys are rejected immediately by **`GET /v1/projects`**.
* Never embed keys in client-side code; call the API from your server.

## See also

* [API Reference overview](/api-reference/introduction) — Base URL, response shape, and endpoint intent.
* [Settings → API Keys](https://suprlogs.com/app/settings/api-keys) — Key management.