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.
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
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
# 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:
{
"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
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.
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.
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.