---
title: API keys
description: Create, rotate, and revoke Trigv workspace API keys. Bearer authentication for event ingest.
---
# API keys

API keys connect your tools to Trigv. You'll need one for Zapier, GitHub Actions, scripts, and most integrations.

## Step 1 — Open the dashboard

<ol>
  <li>Go to <a href="https://app.trigv.com">app.trigv.com</a> and sign in.</li>
  <li>In the left sidebar, click <strong>API Keys</strong>.</li>
</ol>

## Step 2 — Create a key

<ol>
  <li>Click <strong>Create API key</strong> (or similar).</li>
  <li>Give it a name you'll recognize — e.g. <code>Zapier</code>, <code>GitHub CI</code>, <code>Home server</code>.</li>
  <li>Click create. Trigv shows the full key <strong>once</strong>.</li>
  <li>Copy it immediately and store it somewhere safe (password manager, GitHub secret, Zapier header).</li>
</ol>

<div>
  <strong>You can't view the full key again.</strong>
  If you lose it, rotate or revoke the old key and create a new one.
</div>

## Step 3 — Use the key in your tool

Paste the key as a Bearer token — never in the message body:

```
Authorization: Bearer trgv_abcd1234_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
```

Each integration guide shows where to paste this (Zapier header, GitHub secret, etc.).

## Managing keys later

Back in **API Keys** on the dashboard you can:

- **Rotate** — invalidates the old key and gives you a new one
- **Revoke** — permanently disables a key
- **Set expiry** — optional, when creating a key

## Good habits

- Use separate keys per tool or environment (production vs. testing).
- Never commit keys to git or paste them in public Zaps/screenshots.
- Rotate immediately if you think a key leaked.

[API security overview →](/docs/security)