Your catalogue is not a price list we email you. It is read live from the API, already carrying your agreed markup, so it can never drift out of date.

Reading your catalogue

The GetPlans operation returns every plan you are cleared to sell. Each entry carries a code, a name, its product group, and prices for all six billing cycles:

{
  "currency": "USD",
  "markup": 15,
  "count": 4,
  "plans": [
    {
      "code": "388",
      "name": "Linux Hosting - Starter",
      "group": "Shared Linux Hosting",
      "pricing": {
        "monthly": -1,
        "annually": 68.86,
        "biennially": 130.83
      }
    }
  ]
}

The code is what goes into the BIGBANG plan code field on your product. Nothing else identifies a plan.

A price of -1 is not a price

-1 means that billing cycle is switched off for that plan. Do not read it as free or as zero, and do not order on it — the order is refused with cycle_unavailable. Many plans are sold annually only, so their monthly value is -1 by design.

How you are billed

When your customer orders, we raise a real order and a real invoice on your account, at the price GetPlans quoted — markup included. The service appears in your client area with us exactly like any other service you buy from us, and renews on the cycle set in Order on cycle.

What you charge your own customer is entirely your decision. We never see it. It does not have to match your buying cycle either: selling monthly while buying annually is a common and perfectly workable arrangement.

When we change a price

Because the catalogue is read live, a price change reaches you the moment it is made. Existing services keep the price they were sold at until they renew. If you cache plan data on your side, refresh it before you publish prices to your own customers.

Only live plans appear

Retired products are excluded from your catalogue, and they are also refused if ordered by code. If a plan you expect is missing, it has either been retired or is not in your agreement — ask us and we will tell you which.