Least Privilege Examples

Use one token per integration even before strict scope enforcement is added. A backup dashboard can be named Backup Monitor with backups.read; a DNS sync worker can be named DNS Sync with domains.read; a billing reconciliation job can use accounts.read.

Practice

• Name tokens after the integration, not after the person who created them.
• Use comma-separated scope labels that describe intended access.
• Avoid using * for third-party systems unless there is a clear provider-level reason.
• Document who owns the integration and where the token is stored.

PCAdmin

Use PCAdmin → API Tokens to create and review token names, scope labels, status, last used time, and expiry.

Troubleshooting

• For 401, verify token validity and user status.
• For 403, check whether the endpoint requires an admin-capable role.
• For empty results, check whether the token user owns any hosting accounts.