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

# API Keys & Zapier

> Generate and manage API keys that connect Forager to Zapier

API keys let external integration platforms authenticate against Forager on behalf of your company. Today they power the [Zapier integration](/integrations/zapier); each key is scoped to your company and can be revoked at any time.

If you want to push attestations to a specific CMDB endpoint instead, use [Webhook Settings](/dashboard/webhook-settings) — webhooks push to a URL you provide, while API keys let a platform like Zapier pull samples and subscribe to events itself.

## Where to find it

In the web dashboard, go to **Settings** and scroll to the **API Keys & Zapier** section. You must be logged in as an admin.

## Generating a key

<Steps>
  <Step title="Name the key">
    Enter a name that describes where the key will be used, e.g. `Zapier`. The name is only for your reference.
  </Step>

  <Step title="Click Generate key">
    The full key (starting with `frg_`) is displayed **exactly once**, in an amber callout. Copy it immediately — after you dismiss the callout or reload the page, only the key's 8-character prefix is ever shown again.
  </Step>

  <Step title="Store it where it will be used">
    Paste the key into the integration that needs it (for Zapier: the **Connect Account** dialog in the Zap editor). If you lose a key, revoke it and generate a new one — there is no way to recover the full value.
  </Step>
</Steps>

<Warning>
  Forager stores only a cryptographic hash of the key, never the key itself. Anyone with the full key can read your company's attestation data, so treat it like a password.
</Warning>

## The key list

Each key row shows:

| Column        | Meaning                                                                                                                             |
| ------------- | ----------------------------------------------------------------------------------------------------------------------------------- |
| **Name**      | The label you chose at creation                                                                                                     |
| **Prefix**    | The first 8 characters (e.g. `frg_a1b2…`) — enough to match a key against the value stored in your integration                      |
| **Created**   | When the key was generated                                                                                                          |
| **Last used** | The most recent time any integration authenticated with this key. Useful for spotting keys that are no longer in use                |
| **Revoked**   | A badge shown on keys that have been revoked. Revoked keys are kept in the list for audit purposes but can never authenticate again |

## Revoking a key

Click **Revoke** next to an active key and confirm. Revocation takes effect immediately:

* The key can no longer authenticate — any integration using it receives `401 Unauthorized`.
* All Zapier subscriptions created with that key are deleted, so any Zaps connected through it stop receiving events at once.

Revocation cannot be undone. To restore an integration, generate a new key and reconnect.

## Active subscriptions

Below the key list, the **Active subscriptions** panel shows every live event subscription created through your API keys — one row per Zap trigger that is currently turned on, with the provider, the event it listens for (**New Attestation** or **Mismatch Detected**), and when it was created.

This list is read-only and maintained automatically: rows appear when a Zap is published or turned on, and disappear when the Zap is turned off, deleted, or its key is revoked. If a Zap has gone silent, this is the first place to check — no row here means Zapier is no longer subscribed.

## Related pages

* [Zapier integration guide](/integrations/zapier) — building Zaps on Forager triggers
* [Make.com integration guide](/integrations/make) — uses webhooks rather than API keys
* [Webhook Settings](/dashboard/webhook-settings) — direct push to a CMDB endpoint