Connect WHMCS to WHM so your own reseller business can provision and manage the hosting accounts it is authorised to control. This is an administrator integration, not a normal Nabtech client-area login task.
IN THIS ARTICLE
Check access and requirements
Use a supported WHMCS installation and the server’s actual hostname. The HTTPS certificate must match that hostname. Obtain the reseller username and a WHM API token with the permissions required by the WHMCS cPanel module. Do not use a root credential unless you administer the server and need that scope.
01 Connect a cPanel reseller server to your own WHMCS
- In WHM, create a dedicated API token for this integration and record it securely. Limit its privileges and source IPs where the server offers those controls.
- In WHMCS, open System Settings > Servers and add a server using the cPanel module. Enter the supplied hostname, reseller username and token in the module’s API-token field.
- Enable the secure connection and run Test Connection. Enter the server details required by the form, then save it.
- Create or select a server group and add this server. Assign the group to the intended products so provisioning reaches the correct reseller account.
- Create a hidden test product mapped to a valid WHM package. Test one controlled account before enabling customer-facing automation.
02 Example: record the connection and product relationship
Create a short internal mapping for the integration before enabling automation:
| Setting | Value to verify |
|---|---|
| Hostname | The supplied WHM hostname matching its HTTPS certificate. |
| Username | The reseller account permitted to manage these customers. |
| API token | A dedicated token stored in the protected module field. |
| Server group | The group selected by the intended WHMCS products. |
| Package | The exact package available to that reseller on this server. |
Run Test Connection, then provision one controlled test account. Verify its server and package in both WHMCS and WHM.
Expected result: the connection, product selection and remote permissions work together, rather than only passing a network check.
Confirm the expected result
Confirm the connection succeeds over trusted HTTPS and that the module can see or use the reseller’s packages. A successful network connection alone does not prove permission to create accounts.
Why does the WHMCS server connection report certificate or permission errors?
For certificate errors, correct the hostname or certificate rather than disabling verification. For access errors, check token permissions, expiration and IP restrictions. Revoke unused tokens after a migration and redact tokens from tickets and logs.