Quick answer
The video shows a deprecated WHM remote access hash. New integrations should use supported, narrowly scoped API tokens instead of copying a broad access hash into a script.
Applies to
For an authorized reseller or administrator whose Interactive Online service includes the relevant WHM permission. Ordinary website hosting uses cPanel and does not imply WHM or root access. Work only with accounts you own or are explicitly authorized to administer. The video is an older interface reference.
Steps
- Identify the integration's exact required WHM operations and confirm reseller authorization. API access is separate from SSH keys.
- If the service permits it, open Development > Manage API Tokens and use the integration's current supported token flow. Choose only required privileges and an appropriate expiry where offered.
- Store the token server-side in protected configuration. Test a harmless authorized operation before provisioning or deleting accounts.
- Keep an inventory and revoke the integration's access when it is no longer needed. Do not enable deprecated access-hash authentication to match the video.
Check the result
Confirm that required operations work and unintended operations are not granted. Keep tokens out of logs, browser scripts and public chatbot content.
Troubleshooting and support
For a legacy integration, coordinate a migration with support before rotating or revoking its credential. Never post the hash or token in a ticket.
If the problem continues, contact support from the account that owns the service. Include the domain, exact error, time and time zone, tool name, and a redacted screenshot. Keep passwords, private keys, cookies and private message content out of the ticket.
Video tutorial
The original video is preserved. Its interface or product version may differ from the written guidance above.
Related help
Official references
Written content reviewed November 1, 2026. Menu availability depends on the product version, permissions and service.
