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

# Unkey

> Add an HTTP log drain in the Unkey dashboard pointed at your Sazabi intake URL to forward API key verifications, rate limits, audit logs, gateway requests, and runtime logs.

[All Unkey integration capabilities](https://docs.sazabi.com/catalogs/integrations/unkey)

## About

Stream your Unkey API key verifications, rate limit decisions, audit logs, gateway HTTP requests, and runtime logs into Sazabi. Set up an HTTP log drain in Unkey that points at Sazabi, and Unkey sends your workspace events automatically. There is no agent or sidecar to deploy.

## Prerequisites

* An active Unkey workspace with access to the **Log Drains** feature.
* Your Sazabi intake URL (shown above).

## Set up in the dashboard

**Step 1**

### Open the log drain form

In the [Unkey dashboard](https://app.unkey.com), navigate to **Settings > Log Drains** and click **Create Log Drain**.

**Step 2**

### Configure destination and stream

Fill in the log drain fields:

* **Name**: `Sazabi` (or a descriptive name for this destination)
* **Stream**: Select the stream you want to export (**Key verifications**, **Rate limits**, **Audit logs**, **Gateway HTTP requests**, or **Runtime logs**)
* **Destination**: `HTTP`

**Step 3**

### Set URL and encoding

* **URL**: Paste your Sazabi intake URL (shown above)
* **Encoding**: `JSON` (or `NDJSON`)

**Step 4**

### Save and verify

Click **Create Log Drain**. Unkey begins sending log batches to Sazabi immediately.

## Set up with the CLI

You can also register the Unkey log source with the [Sazabi CLI](https://docs.sazabi.com/reference/cli.md) (installed and authenticated — see [CLI reference](https://docs.sazabi.com/reference/cli/log-sources.md)).

Registering the source mints the same intake URL the dashboard shows above (the public key is embedded in its hostname):

```bash theme={"system"}
sazabi log-sources create unkey --mode manual
```

The command prints the intake URL for the new source — copy the whole URL and paste it into Unkey's HTTP log drain URL field. Run `sazabi log-sources get <log-source-id>` at any time to reprint the endpoint, or `sazabi log-sources list` to see every log source in the project.

## Verify

Verify an API key, trigger a rate limit check, or route a request through Unkey Gateway to generate log activity. Open the [Intake page](https://docs.sazabi.com/guides/instrument/intake.md) in the Sazabi dashboard and confirm logs from the **Unkey** source appear. Logs typically arrive within a few minutes of the activity.

## Troubleshooting

**No logs after saving the drain** — Confirm that the destination URL in Unkey matches your Sazabi intake URL, and check the delivery logs under **Settings > Log Drains > \[Your Drain]** in the Unkey dashboard to verify that delivery attempts are succeeding with a `200` status.

**Log drain failing** — If Unkey marks the drain as failing, check the delivery logs on Unkey to inspect the diagnostic response body and verify your network connectivity.

## Further reading

> [card] [Intake](https://docs.sazabi.com/guides/instrument/intake.md)
>
> See per-source ingestion volume and health in the Intake page.

> [card] [Instrument](https://docs.sazabi.com/guides/instrument.md)
>
> Learn how to send data to Sazabi.

> [card] [Log sources](https://docs.sazabi.com/catalogs/log-sources.md)
>
> Browse the full log source catalog.


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