Back
Reseller & API

Reseller API overview (sell VPS, game, bot and app hosting under your brand)

What the Victus Reseller API is, what you can sell with it, and how the prepaid credit model works so you can build your own storefront on top of Victus infrastructure.

resellerapioverviewwhite-labelcredits

The Victus Reseller API lets you provision and manage hosting on Victus infrastructure programmatically, so you can run your own store, dashboard or Discord bot and sell services under your own brand. Your customers never need a Victus account — you own the relationship, set your own prices, and Victus bills you at wholesale via prepaid credits.

What you can sell

  • VPS — full KVM/libvirt virtual machines (Ubuntu templates, SSH root access, snapshots, rescue mode). Category code vps.
  • Game servers — Minecraft (Paper/Purpur/Spigot/Fabric/Forge/Vanilla/Velocity) and other games, provisioned as panel servers. Category code game.
  • Discord bots — Node.js/Python/Java bot hosting plus Lavalink. Category code bot.
  • App hosting — Code-Server, Nginx/PHP/WordPress, databases and more. Category code app.

One base URL, four categories

Every service type is provisioned through the same endpoints. You pass a category (vps, game, bot, app) and a plan code from the catalog — there are no separate APIs to learn per product.

How the prepaid credit model works

Reselling is prepaid. You top up a credit balance on your Victus account (credits are the platform currency, roughly 1 credit ≈ 1 USD), and every service you provision draws down that balance on its billing cycle. Credits are shared with the rest of your Victus account, so the same balance you see in the billing portal is the balance the API spends.

  • Provisioning a service reserves/charges credits for the current cycle — a 402 error means your balance is too low.
  • Recurring renewals are debited automatically each cycle; keep enough headroom so active customer services never lapse.
  • Terminating a service stops future charges. Check GET /account/transactions for the full ledger.
  • You bill your own customers however you like (higher price, different currency) — that is entirely on your side.

Keep a credit buffer

If your balance runs out, active customer services can be suspended on their next renewal. Automate a low-balance alert against GET /account and top up before you hit zero.

The rest of this category walks through getting a key, authentication, the response format, reading the catalog, provisioning and managing services, and receiving webhooks.

Related in Reseller & API

Get an API key and understand the prepaid credit modelMint a reseller API key (rslr_...) from the Reseller API page in the Victus panel, store it safely, and top up the prepaid credit balance the API spends.Authentication and base URLThe Reseller API base URL, how to send your rslr_ bearer token, required headers, and a quick authenticated request to confirm your key works.Response format, errors, rate limits and scopesThe standard success {data} and error {errors:[{code,status,detail}]} envelopes, common HTTP status codes, the 240 req/min rate limit, and how key scopes restrict access.List the catalog, plans and regionsRead the available product categories, plans and pricing with GET /catalog, drill into a specific plan code, and list deployment regions with GET /regions.Provision a service (VPS, game, bot and app examples)Create services with POST /services for every category — full curl examples for a VPS, a Minecraft game server, a Discord bot and an app, plus how to poll until it is ready.Manage a service (power, console, usage, lifecycle, backups)Control a provisioned service: power signals, console access, usage stats, suspend/unsuspend, reinstall, resize, reset-password, backups and termination.List services, get a single service, and check your balanceUse GET /services to list everything you have provisioned, GET /services/{id} for one service, GET /account for your credit balance, and GET /account/transactions for the ledger.Webhooks (events and X-Victus-Signature HMAC verification)Register a webhook endpoint with PUT /webhooks, receive service and billing events, and verify every delivery with the X-Victus-Signature HMAC header.