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

# Authentication

> Create a team API key and authenticate Wirespeed API requests

For programmatic access to the public API, use a **team API key** sent as a Bearer token. Browser sessions authenticated through the Wirespeed UI also work on `/v1` endpoints, but integrations and automation should use a team API key.

## Create an API key

1. Sign in as a team **Admin** (only Admins can access Team API Keys).
2. In Wirespeed, open **Settings → Team**.
3. Scroll to **Team API Keys**.
4. Create a key with a name, [role](/settings/roles), and expiration (1–720 days).
5. Copy the token immediately — it is shown **only once**. Keys are prefixed with `wspd-`.

See [Team Settings](/settings/team) for full details on team API keys and permissions.

<Warning>
  If you lose a team API key, delete it and create a new one. Existing keys cannot be viewed again after creation.
</Warning>

## Send the key with requests

Include the full key (including the `wspd-` prefix) in the `Authorization` header:

```bash theme={null}
curl https://api.wirespeed.co/v1/... \
  -H "Authorization: Bearer wspd-YOUR_TEAM_API_KEY"
```

In the API playground on each endpoint page, paste the same value into the **Authorization** field (Bearer token).

<Warning>
  Do not paste production API keys into shared or untrusted API playgrounds. Prefer curl or your own test environment when handling real credentials.
</Warning>