Toplink DCIM for WHMCS
Already running on WHMCS? Install the Toplink DCIM module and WHMCS keeps handling sales and invoices while DCIM delivers servers and self-service. No need to start over.
Key capabilities
- 01
Provisioned on payment
A server is allocated from DCIM, the OS installed, and the hostname and IPs filled back automatically.
- 02
Bind existing servers
If a machine is already prepared in DCIM, enter its server ID to bind it to the order.
- 03
Client-area self-service
Power on and off, reinstall, VNC, hardware and port traffic, with each permission controllable.
- 04
Configurable options
Bandwidth, extra IPs and hardware can be ordering options that feed into the price.
Before you connect
| Check | How |
|---|---|
| DCIM has a user group | Users → User groups in the admin panel is not empty |
| DCIM has plans, and servers for sale are bound to one | The server’s assignment details show a plan |
| DCIM has a data center and available OS images | Required for provisioning and installation |
| You know WHMCS’s PHP version | The module is packaged per PHP version |
| ionCube Loader is installed | Required to load the module |
| WHMCS can reach DCIM | DNS, firewall and certificates are all in place |
Setup steps
- In DCIM: create a user group and plans and bind servers, then generate a key and secret under System API, optionally allowing only the WHMCS server’s outbound IP;
- Install the module: upload the package for your PHP version;
- Add a server: choose the “Toplink DCIM” module, enter the key as username and the secret as password, and tick SSL if DCIM uses https;
- Custom settings: set the username prefix, hostname format and more;
- Create products: choose the node, data center and plan, and enable automatic provisioning.
Common custom settings
- Username prefix: DCIM accounts are the prefix plus the WHMCS user ID, which must differ when several WHMCS sites share one DCIM;
- Hostname format: if a customer enters an invalid hostname, one is generated from placeholders such as
{label}-{ipv4}; - Reseller mode: connect through the reseller API;
- Force English: keep the interface in English for international customers.
Automated lifecycle
- Order paid: server allocated, OS installed, hostname and IPs filled back;
- Overdue: server shut down and disconnected, then restored on renewal;
- Terminated: server unbound and IPs released.
For detailed field descriptions, see “Toplink DCIM integration with WHMCS” in the product documentation.
FAQ
Can one DCIM connect to several WHMCS installations?
Yes. Give each WHMCS site its own username prefix so users with the same ID on different sites do not collide in DCIM.
What are the environment requirements?
The WHMCS server needs an ionCube Loader matching its PHP version; the module is packaged per PHP version.
How are overdue and terminated services handled?
Overdue servers are shut down and disconnected automatically and restored on renewal. Terminating a service unbinds the server and releases its IPs.
See how it works in your data center.
Start with a product demo and map out your next step.
Hotline 400-112-2951