Every account on this panel has API access by default, and the whole surface is built around six endpoints — enough to run a fully automated reseller storefront without ever touching the admin panel by hand.
The starting point is the services endpoint, which returns the full catalog: every active service's ID, name, category, min/max order size, and the panel's rate per 1,000 units. That rate is your cost — what you build a storefront on top of is your own markup on top of it, applied in whatever way suits your business (a flat percentage, a fixed markup per category, tiered pricing for volume). The panel itself never sees or cares what you charge your own customers; from its side, an API order is just an order.
Placing an order takes a service ID, the link or username the service expects (services differ on this — check the service's link_type before submitting, since a username-based service rejects a full URL and vice versa), and the quantity. A successful call returns an order ID on this panel's side, which is the only thing you need to store to track that order going forward.
Status polling is the endpoint you'll call most often — pass the order ID back and get the current status (pending, in progress, completed, partial, canceled) along with the remaining quantity if the service tracks it. A reasonable reseller setup polls open orders every few minutes rather than constantly, since status only changes when the underlying provider actually updates something.
The balance endpoint returns your current wallet balance in the panel's base currency, worth checking before a bulk of orders goes out so a low balance doesn't turn into a batch of failed submissions partway through. Refill and cancel endpoints exist for services that support them — refill re-triggers delivery on a dropped order within its refill window, cancel stops a service (like a subscription-style order) that hasn't finished yet.
A minimal working reseller loop is: pull the catalog on a schedule to keep local prices current, accept an order from your own customer, submit it through the order endpoint, store the returned ID, and poll status until it resolves. Everything past that — payment collection, customer accounts, your own markup logic — is entirely up to how you want to run the business on top of it.