---
title: Create API keys
description: Issue and revoke per-event API keys for your own integrations.
sidebar:
  badge: Starter+
---

Every event can issue API keys for your own automation and scripts: score trackers, custom dashboards, CI jobs. Keys are managed per event on the **API keys** page of the event dashboard.

API access is included on Starter and above; on the Hobby plan the API keys page doesn't appear in the sidebar.

## Find your API URL

The **API URL** card at the top of the page shows the base URL for your integration requests, with a copy button. It's derived from your event's address, so it appears once your event is provisioned and its site is up.

Requests authenticate with a bearer token: send your key as `Authorization: Bearer <token>`.

## Create a key

1. Click **Create key**.
2. Optionally give it a **Label** (e.g. *CI*, *analytics bot*) so you can tell keys apart later.
3. Pick **Expires in**: **7 days**, **30 days**, or **90 days** (the default). Keys always expire; 90 days is the maximum lifetime.
4. Click **Create key**.

The dialog then shows your new key **once**: *"This is the only time the full token is shown. Store it in your secure password/vault manager. It cannot be retrieved again here."* Copy it before clicking **Done**; closing the dialog discards it for good.

## Review and revoke keys

The key table lists every key with its label, created and expiry times, and status, either **Active** or **Expired**. Expired keys stay listed for your records.

To revoke a key, click its trash button and confirm in the **Revoke API key?** dialog; the key is disabled immediately. Revoking requires your event's site to be up, since the key is disabled on the event itself.

:::note[Keys don't survive a downgrade]
If your workspace moves to a plan without API access, the event's API keys are revoked automatically and integrations using them stop working. If a key can't be revoked right away, for example while the event's site is unreachable, it stays in the list so you can revoke it yourself. Creating new keys requires a plan with API access.
:::
