icon
StandMap API

Quota

Quota is a prepaid count of subscriptions you may issue, held separately for each product. One unit becomes one subscription.

Checking your balance

GET /v1/billing/partner/balances API key

Takes no parameters — the account is determined by your credentials. Returns a plain array, not a paged envelope.

200 OK 
[
  {
    "productSlug": "standoff_radar_high_30days",
    "productName": "Radar High — 30 days",
    "balance": 412,
    "initiated": 500
  },
  {
    "productSlug": "standoff_radar_low_lifetime",
    "productName": "Radar Low — lifetime",
    "balance": 8,
    "initiated": 20
  }
]
Response items
productSlug string

The identifier you pass as planSlug when issuing. This is the authoritative list of what you can spend against.

productName string

Human-readable name, for your own dashboards.

balance integer

Units available to spend right now.

initiated integer

Lifetime total ever credited to you for this product. Not a period opening balance.

Read your slugs from here. Product slugs are not fixed constants you should hardcode from examples. A product you have never been credited for simply will not appear in this list.

Topping up

Quota is credited by us, on agreement — there is no endpoint to buy it programmatically and no way to top yourself up from the panel. Get in touch when you need more, and it appears on your balance as a Topup entry.

How spending works

Issuing a subscription costs one unit; generating a batch of promo codes costs one unit per code, charged when the batch is created rather than when a code is redeemed. Both are checked against your balance before anything is granted.

Quota can never go negative. If you ask for more than you hold, the request is refused in full with Reseller.InsufficientQuota and nothing is consumed. There is no partial fulfilment — a batch of 50 codes against a balance of 30 issues zero codes, not 30.

Concurrent requests are serialised per account, so two calls arriving at the same moment cannot both spend the last unit.

Refunds

There is no refund endpoint. Quota comes back automatically in one case: a promo batch that was charged but could not be generated is credited back in full, and the response tells you no quota was consumed.

A subscription already issued to a user is not reversible through the API. Nothing is ever deleted from your history — a reversal is recorded as its own credit entry alongside the original charge, so the ledger in the panel always shows both.

Expiry

Quota does not expire. Once credited it stays on your balance until you spend it.