Orax Orax
Sign in

Reseller API & webhooks

2 min read13.10.202696 views
On this page

The reseller API lets you run your clients' services programmatically — from the order to managing the site inside the account.

Access

A personal reseller key: the live one starts with rsk_…, the sandbox with rsk_test_…. A rate limit applies (60 requests a minute).

What you can do

  • Account and catalogue: balance, limits, wholesale and retail prices (a currency can be requested by parameter).
  • Ordering a service and its lifecycle: suspend, unsuspend, freeze, unfreeze, terminate.
  • Renewal: extend by N periods and switch auto-renewal on. This matters — without auto-renewal or an explicit renewal a client's service dies at the end of its first period.
  • Tariff change: the list of available plans and the switch itself.
  • Panel login on the client's behalf: a one-time panel session so your client gets inside without a separate password.
  • Managing the account's contents: domains, DNS, databases, FTP, mail, SSL, cron, PHP, logs, files (uploads and undo included), SSH keys, shell, backups.
  • Watching: uptime, usage, security scans, monitors.
  • Buying a template at wholesale onto a client's service.

About money

Amounts arrive as {usd_cents, currency, amount, display}: usd_cents is what is always counted, the rest is for showing your client.

Renewals are prepaid: the credit limit covers the initial order only.

Webhooks

Service events arrive as signed POST requests — verify the signature on your side. If your endpoint fails ten times in a row we disable the webhook and tell you: a dead endpoint must not pile up a queue for ever.

Tips

  • Test the integration in the sandbox first.
  • Keep the key secret; reissue it if it leaks.
  • Tag services with your own client_ref — that is how you tie them to your clients.

An agent on your key (mcp)

The same key attaches an AI agent, over the MCP standard, at https://orax.uz/api/v1/reseller/mcp. The key goes in as an ordinary Bearer token; no separate authorisation is needed.

What the agent can ask:

  • Account standing: balance, markup, wholesale spent.
  • The catalogue with both prices at once — wholesale and the suggested retail at your markup.
  • Your services: by one client (client_ref), by status, or only those expiring within N days. Every row says whether the service renews itself.
  • One service in detail: expiry, whether it needs acting on, whether the site opens and how many days are left on the certificate.

What the agent cannot do: order, renew, or spend your balance. That stays on the ordinary API methods, where a human wrote the integration.

Was this helpful?