Automating hosting operations with PCCLI and the API
Two automation surfaces, one audit trail: when to reach for the terminal and when to reach for the REST API.
PanelConfig gives you two ways to automate: PCCLI on the server and a scoped REST API over HTTPS. They drive the same records and the same job queue, so scripted work stays inside the audit trail.
When to use PCCLI
Use the pc command for on-server automation: cron-driven backups, account lifecycle, draining the job queue, and health checks. It is the natural fit for anything running on the box itself.
pc accounts:list
pc ssl:issue --domain-id=31
pc jobs:run-next
When to use the API
Use the REST API for remote integrations: dashboards, provisioning from another system, or monitoring. Tokens are scoped, rate limited, and hashed at rest.
The shared guarantee
Whichever you choose, the action becomes a record and, where relevant, a queued job. Automation never bypasses the controls the panels enforce.