Create an installation-local connection
Open Security → API Tokens in your current local Admin or Customer identity. Token creation/revocation requires fresh authentication. Choose a printable connection name of 1–80 characters, lifetime of 1 hour, 24 hours, 7 days or 30 days and only the scopes returned as available by the server. Review before creating.
The secret is shown once. Reveal/copy it privately into your integration's secret store and confirm it was saved before closing. It is never listed again; revoke a lost token and create a replacement. A token cannot sign in to a browser or Linux root.
Exact scopes
| Scope | Supported boundary |
|---|---|
hosting:inventory:read |
Installation-owner-only account/package inventory and dated recorded usage; use alone in a separate token. |
resources:read |
Permitted hosting resource metadata; excludes file contents, passwords and server control. |
operations:read |
Permitted task history and progress. |
operations:write |
Supported permitted task submission/cancellation; not automated account administration. |
Customers cannot obtain server-wide hosting inventory. Current local identity, grants, epoch, expiry and revocation are rechecked on requests. Creating a token does not freeze its owner's permissions indefinitely.
Hosting/billing inventory endpoints
Use verified HTTPS to your own Panel origin and Authorization: Bearer <token>. The exact owner inventory routes are GET /admin/v1/integrations/accounts, /admin/v1/integrations/accounts/{id} and /admin/v1/integrations/packages. IDs are 32 lowercase hexadecimal characters. Read cursor pages and distinguish observation time/unavailable usage from actual current enforcement.
These endpoints permit a billing application to inspect existing hosting resources. This inventory token cannot create/change accounts. Newer source provides separately scoped owner-only suspension/reactivation; see the activation integration guide. Account creation, package changes and termination remain outside that integration. There are no WHM-compatible gateway/registrar drivers, root commands or customer-billing suite in Panel. Do not configure a billing connector to call private browser lifecycle routes as if token ownership authorized them.
Inventory and revocation
GET /auth/{admin|customer}/tokens?limit=25 lists metadata and available scopes. Creation posts name, scopes, expires_hours to /tokens; revocation posts the token metadata id to /tokens/revoke. Verify revoked: true and refresh; already accepted work may continue under its existing operation contract. A capacity error requires revoking unused connections rather than generating unbounded credentials.
Verify without business changes
Test a read with the intended scope, an unrelated resource denial and a new request after revocation. Never put a bearer token in a query string or public screenshot. Unknown routes/scopes fail closed. A signed extension uses its separate short-lived bound credential contract; do not hand it a long-lived general inventory token.