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

# API Key Management

> Create, manage, and revoke API keys for programmatic access to Moonbounce

## Overview

Admins can create, view, and revoke API keys directly from the Moonbounce dashboard. API keys provide programmatic access to the Moonbounce API for your integrations and automated workflows.

To manage API keys, navigate to **Account Settings → API Keys**.

<Note>Only users with the **Admin** role can access and manage API keys.</Note>

## Creating an API Key

1. Go to **Account Settings → API Keys** and click **Create API Key**.
2. Enter a descriptive **name** for the key (e.g. "Production API Key").
3. Choose an **expiration** for how long the key should remain valid:
   * 30 days
   * 90 days
   * 180 days
   * 365 days
   * No expiration
4. Click **Create**.
5. **Copy your API key immediately.** The full key is only shown once and cannot be retrieved later.

## Using Your API Key

Include your API key in the request headers when calling the Moonbounce API:

```bash theme={null}
curl -H "Authorization: Bearer YOUR_API_KEY" \
  https://api.clavata.ai/v1/jobs
```

For SDK usage, refer to the [Python SDK](/integrations_and_developer_tools/api-docs-sdks/python_sdk), [JavaScript/TypeScript SDK](/integrations_and_developer_tools/api-docs-sdks/javascript_typescript_sdk), or [Go SDK](/integrations_and_developer_tools/api-docs-sdks/go_sdk) documentation.

## Managing Existing Keys

The API Keys page displays all keys for your account, including:

| Column        | Description                                                             |
| ------------- | ----------------------------------------------------------------------- |
| **Name**      | The label you assigned when creating the key                            |
| **Owner**     | The email of the user who created the key                               |
| **Status**    | Enabled, Disabled, or Revoked                                           |
| **Created**   | When the key was generated                                              |
| **Expires**   | When the key will expire (or **No expiration**), color-coded by urgency |
| **Signature** | The last 6 characters of the key for identification                     |

### Key Actions

From the actions menu on each key, you can:

* **Disable** — Temporarily deactivate a key. It can be re-enabled later.
* **Enable** — Reactivate a previously disabled key.
* **Revoke** — Permanently invalidate a key. This action cannot be undone.

## Best Practices

* **Rotate keys regularly.** Create a new key before revoking an old one to avoid downtime.
* **Use descriptive names.** Name keys after their intended use (e.g. "CI Pipeline", "Staging Environment") so you can easily identify them later.
* **Revoke unused keys.** If a key is no longer needed, revoke it promptly to reduce your attack surface.
* **Never share keys in plaintext.** Store API keys in environment variables or a secrets manager, not in source code.