API keys
Connect your application to your UNode account.
Create a key
Sign in to API keys in the console, choose a name and permissions, then copy the token. The complete token is shown only once. Store it in your server's secret manager.
Make a request
curl https://api.unode.net/v1/servers \
-H 'Authorization: Bearer YOUR_API_KEY'
Use the Authorization header on every request. Keep keys out of browser bundles, URLs, public repositories and customer VPSs.
Permissions
Server and billing permissions each support none, read or write. Write includes read. Grant only what your integration needs. A reseller normally needs server write and billing write, with admin set to none. Admin permission does not turn a customer account into an administrator.
Keys act on the account that created them. Account-wide keys can purchase servers; restricted keys cannot manage account-wide billing or subscriptions. API-key creation, listing and revocation require a signed-in console session.
Rotate or revoke
Create a replacement, update your application and verify a request, then revoke the old key in the console. Revoking a key stops its access; it does not delete your servers.
Next: reseller integration · webhooks