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

# API keys

> Create a key for each system, choose what it can read, and revoke it when the system no longer needs it.

## Create a key

On the [API's page](https://portal.schoolcues.com/settings/integrations/api), choose **Create API Key**, then:

1. Name the system the key is for.
2. Under **Can Read**, choose which resources it may read: students, contacts, staff, classes or payments.
3. Under **Expires**, choose never, 30 days, 90 days or a year.
4. Copy the key and the base URL from **Copy Your API Key**.

> [!WARNING]
>
> The key is shown once. Store it in your system's secret store before you close
> the dialog.

A new school may see a message to try again in a few minutes. Its keys become available once SchoolCues finishes setting up the school's sign-in organization.

## Send the key

Send the key as a bearer token with every request:

```bash theme={null}
curl https://BASE_URL/api/school/v1/students \
  -H "Authorization: Bearer sk_..."
```

Use the base URL from **Copy Your API Key** in place of `BASE_URL`.

## What a key can read

Each resource needs its own permission, such as `students:read`. A key without the permission for a resource gets a `403` response that names the resource.

## Review and revoke keys

The **API Keys** section lists each key's name, what it can read, the end of the key, when it was created and last used, and when it expires. Choose **Revoke** in a key's row menu to stop it at once.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.