API
The REST API the dashboard uses, and the contract the CLI posts to.
The REST API the dashboard uses, and the contract the CLI posts to.
In this section
- Authentication How to authenticate against the CaptainCore REST API with application passwords, how the dashboard authenticates, and what non-admin scoping means.
- Running commands and jobs Execute WP-CLI and shell code across environments, choose between synchronous and queued execution, then poll, stream or cancel the resulting job.
- Sites and environments Read and manage sites, their production and staging environments, files, domains, admin tools, stats, performance samples and logs.
- Domains, DNS and accounts Manage domains and their DNS zones, registrar settings, email forwarding and Mailgun sending, plus accounts, users, invites and billing.
- Security and operations Fleet security operations, threat tracking and patches, checksum failures, site audits, activity logs, reports, archives, recipes, providers and settings.
- CLI ingest contract The token-authenticated POST /api endpoint the CaptainCore CLI posts to, every command it accepts, and the key:value format the remote data collector returns.
- Endpoint index Every route registered under captaincore/v1, with its methods and permission requirement, grouped by area.