Manage API Tokens
Create scoped API credentials for approved integrations.
1Overview
Manage API Tokens creates credentials for external systems using selected privileges, expiration, integrations, and network restrictions. Sensitive actions require administrator password verification.
2Before you begin
Administrator actions can affect multiple customer accounts and server services. This is a security-sensitive task; use the narrowest change that solves the verified issue.
3Step-by-step workflow
Open Manage API Tokens, create or select an integration, choose the least privileges required, set an expiration and allowed networks where possible, complete verification, then copy the token once into a secure secret store.
- Open Manage API Tokens and identify the integration that needs access.
- Choose Create token and give the credential a clear name describing its purpose.
- Select only the scopes needed for account provisioning, deployment, DNS, email, or the supported operation.
- Restrict the token to the intended account or allowed resources where the form supports it.
- Set an expiry and source-IP restriction when appropriate for that integration.
- Create the token and copy its secret once into the integration secret store.
- Test a low-impact operation and check that the returned account and domain are the intended ones.
- Revoke an unused or exposed token and create a replacement rather than reusing a shared administrator password.
4Practical example
Example: an AI website builder that deploys one customer site should use a token with the required account and deployment scopes. A WHMCS integration may require different provisioning permissions.
5Verify the result
Validate the outcome from the affected account or an independent client connection, not only from the administrator screen.
- Test the integration using a non-destructive API request.
- Confirm the token is scoped correctly and cannot perform unrelated actions.
6Common problems and what to check
The token is not shown again: that is expected for a secret stored securely; create a replacement if its original value was lost.
Access is denied: check scopes, expiry, account restrictions, and allowed source addresses.
The wrong account is returned: stop the integration and review its token scope and selected account before any write operation.
7Security, impact, and rollback
A token is equivalent to its assigned privileges. Never place it in browser code, tickets, screenshots, or source control; revoke it immediately when an integration is retired or exposed.