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

# API keys

> Create and manage API keys for programmatic access to Feedal from your own code or integrations.

API keys let you authenticate requests to the Feedal REST API from your own applications, scripts, or tools. Go to **Developers → API Keys** in the sidebar to manage them.

***

## Creating a key

1. Click **Create API key**.
2. Give the key a descriptive name (e.g. "Analytics script", "CI pipeline").
3. Optionally set an expiration — leave blank for a key that never expires.
4. Click **Create**.

**Copy the key immediately.** It is shown in full only once. After you close the dialog, only the prefix (e.g. `sk_live_abc…`) is displayed.

***

## Key fields

| Field         | Description                                               |
| ------------- | --------------------------------------------------------- |
| **Name**      | A label you assign to identify the key                    |
| **Prefix**    | The first characters of the key, shown for identification |
| **Created**   | When the key was created                                  |
| **Last used** | The last time the key was used to authenticate a request  |
| **Expires**   | Expiration date (if set) — blank means never              |
| **Status**    | Active or inactive                                        |

***

## Using a key

Pass the key in the `Authorization` header of every API request:

```http theme={null}
GET /v2/form/ HTTP/1.1
Authorization: Bearer sk_live_your_api_key_here
```

***

## Expiration

Set an expiration date when creating a key to limit its lifetime. Expired keys return `401 Unauthorized`. Create a new key and update your integration before the expiration date to avoid downtime.

***

## Revoking a key

Click the **⋯** menu next to a key and select **Revoke**. Revoked keys are permanently deactivated — any requests using the key will immediately return `401 Unauthorized`. This cannot be undone.

<Warning>
  Revoke compromised keys immediately. If a key is exposed, revoke it and create
  a replacement before updating your integration.
</Warning>

***

## Usage statistics

The **API Usage** tab (next to API Keys) shows request counts, error rates, and per-endpoint breakdown for your keys. Use this to monitor usage and diagnose problems.

***

## Next steps

<CardGroup cols={2}>
  <Card title="API reference" icon="code" href="/developer/api/overview">
    Browse all available endpoints.
  </Card>

  <Card title="Webhook integration" icon="webhook" href="/integrations/webhook">
    Receive events via webhook instead of polling.
  </Card>
</CardGroup>