Reseller & API

List the catalog, plans and regions

Read the available product categories, plans and pricing with GET /catalog, drill into a specific plan code, and list deployment regions with GET /regions.

catalogplanspricingregionscodes

Before you can provision anything, you need a valid plan code and (where relevant) a region. The catalog is your source of truth for what you can sell and what it costs in credits.

List everything

bash

curl https://control.victuscloud.com/api/reseller/v1/catalog \
  -H "Authorization: Bearer $VICTUS_KEY"

This returns all four categories (vps, game, bot, app), each with its list of plans.

Filter by category

bash

# Only VPS plans
curl https://control.victuscloud.com/api/reseller/v1/catalog/vps \
  -H "Authorization: Bearer $VICTUS_KEY"

# A single plan by its code
curl https://control.victuscloud.com/api/reseller/v1/catalog/vps/vps-2c-4g \
  -H "Authorization: Bearer $VICTUS_KEY"

A plan entry describes the resources and the recurring cost in credits. Example shape:

json

{
  "data": {
    "code": "vps-2c-4g",
    "category": "vps",
    "name": "VPS Standard 2/4",
    "specs": { "vcpu": 2, "ram_mb": 4096, "disk_gb": 60 },
    "price": { "credits": 6.0, "cycle": "monthly" },
    "regions": ["de-1", "sg-1"]
  }
}

List regions

bash

curl https://control.victuscloud.com/api/reseller/v1/regions \
  -H "Authorization: Bearer $VICTUS_KEY"

Use a region code from this list (for example the EU and Singapore locations) when you provision. Not every plan is available in every region — the plan entry lists its supported regions.

Cache the catalog

The catalog changes rarely. Cache it for a few minutes rather than fetching it on every page render, so you stay well under the 240 req/min limit.

Never guess a code

Always provision with a code you read back from the catalog. Hard-coded or out-of-date codes cause 404 / 422 errors when plans are renamed or retired.

Related in 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.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.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.