Create client API credentials
Generate a personal client API key in the Victus control panel to automate your own servers, restrict it with an allowed-IP list, and keep it secret.
The control panel exposes a client API so you can script actions against the servers on your own account — read state, send power signals, run console commands, manage files and more — without clicking through the UI. This is the per-user client key, and it is separate from the Reseller API used to provision brand-new services.
Client API vs Reseller API
The client API key created here controls servers you already own. The Reseller API (https://control.victuscloud.com/api/reseller/v1, keys prefixed rslr_) is a different system for programmatically creating and billing new services from a prepaid balance — see the Reseller API docs for that.
Create a key
- 1Sign in to control.victuscloud.com and open your account settings (profile / account menu).
- 2Find the API Credentials / API Keys section.
- 3Create a new key: give it a clear description (e.g. "restart-bot script") so you remember what it is for.
- 4Optionally set an allowed-IP list so the key only works from the machine/server that will use it.
- 5Copy the generated key immediately and store it in a secret manager — it is shown only once.
You only see the full key once
The panel displays the secret a single time at creation. If you lose it, you cannot recover it — delete the key and create a new one. Never commit keys to Git, paste them in Discord/tickets, or hard-code them in client-side apps.
Using the key
Send the key as a Bearer token in the Authorization header. The client API lives under the panel domain. For example, to list the servers you can access:
Find your server ID
A server’s ID is shown on its Settings tab in the panel and in the server URL. Use it in the /api/client/servers/<id>/... endpoints.
Housekeeping
- Create one key per script/integration so you can revoke a single one without breaking the others.
- Delete keys you no longer use — a leaked key can control your servers.
- Lock keys to a fixed IP whenever the calling machine has a stable address.
- Rotate a key immediately if you suspect it leaked, then update your scripts with the new value.