Authentication
Use a browser session for the console and an API key for your backend.
Console access
Sign in at console.unode.net/login using GitHub, Telegram, an email sign-in link, or an existing passkey. Add a passkey after signing in through Settings → Security. Your device or password manager stores its private key; UNode stores only its public key. Never collect your customer's UNode login credentials.
Additional login methods
Connect GitHub explicitly from Settings → Security after a recent sign-in. A matching email address does not silently merge accounts. If GitHub says an account already exists, sign in with your existing method first, then connect it. Add and verify an email before connecting GitHub to a Telegram-only account.
You can name, rename and remove passkeys. Changes require signing in within the last ten minutes; UNode refuses to remove your last usable method. Keep a verified email or Telegram available if a device is lost. VPS root passwords are separate from your UNode account login.
Backend access
Send Authorization: Bearer YOUR_API_KEY to https://api.unode.net. See API keys for creation and scopes. Public catalog endpoints do not require authentication; each operation in the API reference lists its requirements.
Errors
A 401 means the credential is missing, expired or invalid. A 403 means the authenticated principal lacks access. Never solve a 403 by exposing a broader key to the browser.