API Key Revoked

api-key-revoked · 401

The API key behind the call no longer works, though its access token hasn't expired, so the API opened no tunnel.

A token outlives a key revoked after the token was issued, so opening a tunnel checks the key itself. Only a call made with a key's token meets this; a console session never does.

This type adds no members to the ones every error carries.

Common causes

  • The key was revoked after it was traded for the token.
  • The key passed its expiry date.

How to fix the call

  • Ask the user for a key that works, trade it for a new token, then connect again.
  • Don't retry with the same token: the answer won't change.

Example response

json
{
  "type": "api-key-revoked",
  "title": "API Key Revoked",
  "detail": "The API key this call was made with was revoked or has expired.",
  "requestId": "req-1785231000000-4f7b2c9ae",
  "timestamp": "2026-07-28T09:30:00.000Z",
  "path": "/v1/services/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401/tunnels",
  "method": "POST",
  "instance": "POST /v1/services/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401/tunnels",
  "status": 401,
  "docs": "https://ghaym.me/docs/errors/api-key-revoked"
}