---
title: API Keys
description: Authenticate with torqee_ API keys.
---

API keys are `torqee_`-prefixed Bearer tokens for trusted server-side
integrations and agents.

```bash
curl https://connect.torqee.app/api/v1/sessions \
  -H "Authorization: Bearer torqee_YOUR_API_KEY"
```

API keys are issued and revoked in the torqee web app. Connect validates keys
but does not create them.

An API key carries the same scopes as OAuth tokens:

| Scope                     | Allows                                           |
| ------------------------- | ------------------------------------------------ |
| `torqee:sessions:read`    | List sessions and read session metadata.         |
| `torqee:transcripts:read` | Search transcripts and read transcript segments. |
| `torqee:audio:read`       | Get temporary session audio download URLs.       |
| `torqee:boards:read`      | List and read AI board contents.                 |
| `torqee:webhooks:read`    | Read webhook endpoints and delivery history.     |
| `torqee:webhooks:write`   | Manage, test, and replay webhooks.               |

Creating a webhook for a `session.*` event also requires
`torqee:sessions:read`. Fetching a transcript after a completion event requires
`torqee:transcripts:read`. Existing API keys do not gain newly available scopes;
issue a new key when you need webhook or audio access.

Keep API keys secret. They grant workspace access for their configured scopes.