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

# 1. Account and API key

> Get access to the Tavrn Platform and create an API key with the scopes your integration needs.

Access is per organization. Once your organization is onboarded, an organization admin
signs in to the [Tavrn Platform](https://platform.tavrn.ai/dashboard/api) and creates API
keys there. If your organization is not on Tavrn yet, [book a demo](https://www.tavrn.ai/demo).

## Create an API key

1. In the Tavrn Platform, open **API** in the left menu (`platform.tavrn.ai/dashboard/api`).
2. Click **Create API Key** and name it after the system that will use it.
3. Select the permission scopes the integration needs (table below).
4. Copy the key. It is shown once; store it in your secrets manager.

<Warning>
  Keys look like `tavrn_sk_live_…` and are shown only at creation. If a key is lost or leaked,
  create a new one and revoke the old one in the dashboard.
</Warning>

## Scopes for a retrieval integration

| Scope | Needed for |
| - | - |
| `retrievals:write` | Creating, cancelling and answering retrieval requests |
| `retrievals:read` | Reading request status, documents and costs |
| `cases:write` | Creating the case inline on the first request |
| `requestors:read` | Listing your firm profiles |
| `requestors:write` | Creating or updating a firm profile and uploading its documents |
| `webhooks:write` | Registering the endpoint that receives retrieval events |

Add `documents:read` and `documents:write` later if you keep your own case documents in
Tavrn. The full list is in [Authentication](/guides/v2/authentication#permission-scopes).

## Make the first call

```bash theme={null}
curl https://enterprise.tavrn.ai/v2/requestors \
  -H "Authorization: Bearer $TAVRN_API_KEY"
```

A `200` with a `results` array (your organization's default profile is in it) confirms the
key works. A `401` means the key is wrong or revoked; a `403` means the key lacks the scope.
See [Errors](/guides/v2/errors) for the response shape.

<Card title="Next: set up your firm profile" icon="arrow-right" href="/guides/v2/get-started/firm-setup">
  Firm name, letter of representation, invoice approval limit and affidavits.
</Card>