Hono guide

Protect Hono routes with API keys. The code works on Node, Bun, Deno, and Cloudflare Workers. Only how you read the root key changes. Use the @unkey/hono middleware to have verification handled for you, or write a few lines with @unkey/api to control every response.

You need a root key with the permissions listed on this page. Create one in the dashboard under Settings > Root Keys. See Permission reference for every permission.

Create a root key and a keyspace

In the dashboard, go to Settings > Root Keys and create a root key with api.*.create_api, api.*.create_key, and api.*.verify_key. Put it in your server’s UNKEY_ROOT_KEY environment variable. Never send it to a browser or mobile app.Then create a keyspace, which holds your keys. Use Keyspaces (APIs) in the dashboard, or apis.createApi:

create a keyspace

curl -X POST https://api.unkey.com/v2/apis.createApi \
  -H "Authorization: Bearer $UNKEY_ROOT_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "name": "my-api" }'

Keep the data.apiId from the response. You need it to create keys. See Root keys for more on root keys.

Install the SDK

@unkey/hono (version ) is the middleware. @unkey/api (version ) is the client for creating keys and for the hand-written version.

npm install hono @unkey/hono @unkey/api

bun add hono @unkey/hono @unkey/api

Create a key for a user

Create a key from your backend when a user signs up or asks for one. externalId links the key to the user, so verification tells you who’s calling. meta comes back on every verification. You get data.key only once: show it to the user and store only data.keyId.

curl -X POST https://api.unkey.com/v2/keys.createKey \
  -H "Authorization: Bearer $UNKEY_ROOT_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "apiId": "api_...", "prefix": "sk_live", "externalId": "user_123", "meta": { "plan": "free" } }'

import { Unkey } from "@unkey/api";

const unkey = new Unkey({ rootKey: process.env.UNKEY_ROOT_KEY ?? "" });

const created = await unkey.keys.createKey({
  apiId: process.env.UNKEY_API_ID ?? "",
  prefix: "sk_live",
  externalId: "user_123",
  meta: { plan: "free" },
});
// created.data.key is the plaintext, created.data.keyId the handle you keep

Every field is described in Creating keys.

Verify the key in a middleware

With @unkey/hono, the unkey() middleware reads the bearer token, it, and stores the result in the unkey context variable. handleInvalidKey decides the response for a bad key.onError only runs for unexpected responses, such as a 502 from a proxy. A rejected root key, a throttled request, a 500, or a network failure is thrown instead, so catch those in Hono’s app.onError if you want one response for every authentication failure.

import { Hono } from "hono";
import { type UnkeyContext, unkey } from "@unkey/hono";

const app = new Hono<{ Variables: { unkey: UnkeyContext } }>();

app.use(
  "/items/*",
  unkey({
    rootKey: process.env.UNKEY_ROOT_KEY ?? "",
    handleInvalidKey: (c) => c.json({ error: "invalid API key" }, 401),
    onError: (c, err) => {
      console.error("unkey", err.message);
      return c.json({ error: "authentication unavailable" }, 503);
    },
  }),
);

app.get("/items/list", (c) => {
  const verification = c.get("unkey");
  return c.json({ items: [], owner: verification.data.identity?.externalId });
});

export default app;

import { Hono } from "hono";
import { Unkey } from "@unkey/api";
import * as errors from "@unkey/api/models/errors";
import type {
  V2KeysVerifyKeyResponseBody,
  V2KeysVerifyKeyResponseData,
} from "@unkey/api/models/components";

const unkey = new Unkey({ rootKey: process.env.UNKEY_ROOT_KEY ?? "" });
const app = new Hono<{ Variables: { unkey: V2KeysVerifyKeyResponseData } }>();

app.use("/items/*", async (c, next) => {
  const auth = c.req.header("authorization") ?? "";
  const key = auth.startsWith("Bearer ") ? auth.slice("Bearer ".length) : "";
  if (!key) return c.json({ error: "missing API key" }, 401);

  let result: V2KeysVerifyKeyResponseBody;
  try {
    result = await unkey.keys.verifyKey({ key });
  } catch (err) {
    if (err instanceof errors.UnkeyError) console.error("unkey", err.statusCode, err.message);
    return c.json({ error: "authentication unavailable" }, 503);
  }

  if (!result.data.valid) {
    return c.json({ error: result.data.code }, statusFor(result.data.code));
  }
  c.set("unkey", result.data);
  await next();
});

app.get("/items/list", (c) => c.json({ items: [], owner: c.get("unkey").identity?.externalId }));

function statusFor(code: string): 401 | 402 | 403 | 429 {
  switch (code) {
    case "RATE_LIMITED":
      return 429;
    case "USAGE_EXCEEDED":
      return 402;
    case "FORBIDDEN":
    case "INSUFFICIENT_PERMISSIONS":
      return 403;
    default:
      return 401;
  }
}

export default app;

Keep next() outside the try. Otherwise an error in a route handler is caught here and answered as an authentication failure.The middleware also takes permissions (a permission query every key must pass), tags, and getKey (for keys sent somewhere other than the Authorization header).

Handle the outcome codes

keys.verifyKey returns HTTP 200 for every outcome. Check data.valid, then data.code for the reason, and return the matching status from your API:

`data.code`	Meaning	Return
`VALID`	Every check passed.	continue
`NOT_FOUND`	No such key, or your root key may not verify this keyspace.	401
`DISABLED`	The key was disabled.	401
`EXPIRED`	The key’s expiry passed.	401
`FORBIDDEN`	Client IP not on the keyspace allow list, or the workspace is disabled.	403
`INSUFFICIENT_PERMISSIONS`	The `permissions` query was not satisfied.	403
`RATE_LIMITED`	A on the key or its identity was exceeded.	429
`USAGE_EXCEEDED`	The key has no credits left.	402 or 429

Remaining credits are in data.credits, and each checked rate limit is in data.ratelimits with remaining and reset. The call only fails with an HTTP error (which the SDKs throw) when the call itself is wrong, such as a bad root key or a malformed body. See Verifying keys for every field.

Next steps

Verifying keys

Every request field, the order of checks, and every response field.

Credits and refill

Meter usage per key and refill balances on a schedule.

Cookbook

Copy-ready recipes for rate limits, billing, and subscription tiers.

Get started

Framework guides

Keyspaces

Keys

Rate limiting

Identities

Authorization

Analytics

Audit logs

Developer portal

Security

Cookbook

Create a root key and a keyspace

Install the SDK

Create a key for a user

Verify the key in a middleware

Handle the outcome codes

Next steps

Verifying keys

Credits and refill

Cookbook