Documentation / API Token Scopes and Permissions / Scope Troubleshooting

Scope Troubleshooting

Scope Troubleshooting for PanelConfig API permission planning.

When an endpoint returns 403, compare the required role, account ownership, and token scope labels with the token configuration stored in PCAdmin.

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.
← Least Privilege Examples