If you resell licenses at any volume, manually placing each order becomes the bottleneck. Our reseller API removes it: your storefront (or script, or bot) places orders programmatically, pays from your prepaid wallet, and receives the delivered product in the API response or by callback. Here is how the pieces fit together.

The building blocks

  • API account and key. You register once, and your API key authenticates every request — sent as a header. Treat it like a password: server-side only, never in client-side code or a public repo.
  • Wallet. You top up a prepaid balance; each API order deducts your reseller price at the moment of purchase. No per-order payment friction, no card checkout in the middle of an automated flow.
  • Catalog endpoints. List products with live stock status and your specific reseller pricing, so your storefront can display availability truthfully.
  • Order endpoints. Place an order for a product; the response returns the delivered goods (key or account credentials) when fulfilment is instant, or an order ID to poll/receive a callback for otherwise.

A typical integration flow

  1. Sync the catalog. Pull the product list on a schedule; map our product IDs to your own listings; hide anything out of stock.
  2. Customer buys from you. Your site takes the customer's payment through your own gateway at your retail price.
  3. Your server calls the order endpoint with the product ID and your API key. Wallet is debited at reseller price.
  4. Delivery comes back — your system emails or messages it to your customer automatically. The customer experience is instant, and entirely under your brand.
Tip: build the unhappy path first. Handle “insufficient wallet balance” and “out of stock” responses gracefully — queue the order and alert yourself — before polishing the happy path. Automated storefronts fail loudest at 2 a.m.

Operational practices that keep you out of trouble

  • Monitor your wallet balance and alert yourself below a threshold — an empty wallet is the most common cause of failed automated orders.
  • Log every API order with your own order reference, ours, and the delivery payload. When a customer raises an issue weeks later, this log is your support desk.
  • Respect stock signals. Selling items the API reports as out of stock converts your customers' trust into refund requests.
  • Rotate your key if you ever suspect exposure — a leaked key spends your wallet.

Warranty flows through the API too

If a delivered key fails within the product's warranty window, the replacement process works the same as for retail orders — raise the issue with the order reference, and replacement stock is issued against the original order. Your customer never needs to know your supplier exists.

Getting started

The complete endpoint reference — authentication, product listing, ordering, wallet, and callbacks, with example requests — lives at /api-docs. Register an API account, top up a small test balance, and place a sandbox-scale order end to end before wiring up your storefront. If you prefer a ready-made integration and your store runs WordPress, see our WooCommerce plugin article next.

Start at the API documentation, or review reseller pricing tiers at /reseller.