Personal API Keys
Signed-in users can create personal read-only credentials at Settings → Personal API Keys, /settings?tab=api-keys.
Date: 2026-09-30 Purpose and access Signed-in users can create personal read-only credentials at Settings → Personal API Keys, /settings?tab=api-keys. No paid-tier gate is shown on this section; endpoint access remains subject to the account's permissions. This documents the web/Capacitor settings surface, not native-app parity. Workflow Enter a descriptive key name (up to 100 characters). Optionally enter expiry in days (the input accepts 1–3650); blank means no specified expiry. Select Create key. A blank name or pending creation disables the button. Copy the full token from the one-time reveal dialog into secure storage before closing. The list subsequently shows only its prefix and metadata, not a recoverable token. Open /api-reference for supported endpoints. Your own script supplies Authorization: Bearer ; never put a token in public code, chat, screenshots or a URL. To stop access, choose Revoke, check the selected key, then confirm. Cancel keeps it active; successful revocation removes it from the visible list. Results, limits and states The list shows active/expired status, creation, last-use and expiry dates. A spinner precedes the list; an empty list invites creation. Create/revoke errors appear as destructive messages. If clipboard access fails, copy manually from the still-open reveal. The list lacks a dedicated load-error presentation, so an empty-looking result after a connection failure is not proof that no keys exist; reload before creating duplicates. These keys do not grant write, admin or payment rights and are not provider/model API keys. Key management itself requires a signed-in session: a personal API key cannot list, create or revoke keys. The server stores a hash, not a recoverable raw token. Third-party clients store and transmit the credential under their own security controls.