List API Keys
List the API keys of your active account. API keys authenticate requests to the management API via the X-API-KEY header — distinct from agent auth tokens, which are presented by tunnel-server agents at handshake.
Account scope & lifecycle: API keys belong to your active account and act as their creator — each inherits the creator's role permissions in that account, resolved live per request. A key created by a member is tied to that member's account membership: when they are removed from (or leave) the account, their keys for it are revoked automatically (requests return 401). An account owner/admin can also revoke any key bound to the account. Use switch account to manage keys in a different account.
The secret is never returned here: the platform stores only a hash of each key, so key is always the mask "****". The full value is shown once, in the create response. If a key has been lost, delete it and create a new one.
Query parameters
total, page and page_size; when omitted, every key is returned.page is sent. Default 15, capped at 200.description.never (no expiry), expiring (expires within 7 days), active (expires later than that), expired.Response (200 OK)
created_at DESC (newest first). [] when there are none.page was sent: the number of matching keys across all pages, the page returned and the effective page size."****": the key's value is stored only as a hash and can't be shown again. Recreate the key if you've lost it.Deprecated: until the sunset this response also carries the legacy integer id and *_id fields. Don't use them; read uuid and the *_uuid fields.