XUI.ONE Sub Reseller API: WHMCS Integration & Laravel Automation Guide 2026

When you sell reseller credits via WHMCS, use the Sub Reseller API actions directly. The most important provisioning action is create_subreseller.

Critical Rule

Use API actions over authenticated API endpoint. Do not rely on panel UI session handlers for server-to-server provisioning.

Key Actions

create_subreseller – create reseller account
edit_subreseller – update reseller info or credits
disable_subreseller / enable_subreseller
delete_subreseller
get_subreseller / get_subresellers

WHMCS Mapping

CreateAccount: create reseller with starting credits
Renew: add credits using edit action
Suspend/Unsuspend: disable/enable actions
Terminate: delete action

Laravel Implementation Pattern

public function createSubreseller(string $username, string $password, int $credits): array
{
    return $this->call('create_subreseller', [
        'username' => $username,
        'password' => $password,
        'credits'  => $credits,
    ]);
}

Best Practices

Store returned reseller ID immediately.
Use idempotency checks to prevent duplicate provisioning.
Track WHMCS service ID ↔ XUI reseller ID mapping permanently.
Audit all credit adjustments in logs.

FAQ

Q: What action should I use for reseller provisioning?
A: create_subreseller.

Q: How do renewals usually work?
A: Credit top-ups via edit_subreseller.

Related XUI.ONE Guides

Sell XUI Reseller Credits with WHMCS

Launch an automated reseller business model with prebuilt integration modules and lifecycle hooks.

View Product

XUI.ONE Sub Reseller API: WHMCS Integration & Laravel Automation Guide 2026