Sub-resellers and API Print

  • sub-resellers, reseller api, credits, partner accounts, api tokens, white-label, subscriber management
  • 0

Medusa Panel › Account › Manage Accounts

You can resell access without handing out administrator rights. A reseller manages their own subscribers and pays for them in credits; a sub-reseller sits one level below. The same actions are available over the REST API, so a billing system can provision automatically.

Roles

  • Administrator — manages everything and every account, and is not charged credits.
  • Reseller — manages only their own subscribers and the packages they are allowed to sell.
  • Sub Reseller — created by a reseller, one level below, managing their own subscribers underneath that reseller.

Credits

Every account holds a credit balance. When a subscriber’s package is assigned or renewed, its cost in credits is booked against the owner. An administrator tops up a reseller’s balance (Apply Credits); a reseller can pass credits down to its sub-resellers. Administrators are never charged.

An account sees only its own tree. A reseller cannot see another reseller’s subscribers, and a sub-reseller sees only its own — the panel and the API are scoped to the account that is signed in.

Create a reseller

Open Medusa Panel › Account › Add Account. Set its Role (Reseller or Sub Reseller), give it a starting credit balance, and choose which packages it may sell — see Bouquets, prices and limits.

Do it over the API

Everything above is scriptable over the REST API: create subscribers, assign and renew packages, and read usage. A billing platform such as WHMCS can call it to provision accounts the moment an order is paid. Authenticate first, then call the endpoints:

An API caller is scoped like the account it authenticates as. A reseller token can see and change only that reseller’s subscribers, so issue each integration its own account.

Related


Was this answer helpful?

« Back