Sites and environments

A site in CaptainCore is a row in captaincore_sites plus one or more rows in captaincore_environments, typically Production and Staging. Almost everything on this page is scoped to the accounts you belong to.

Remember the casing rule: path segments want lowercase production or staging, while POST /sites/cli and the settings routes want capitalized Production, Staging or Both.

Sites

GET /sites returns lightweight listing records. Auth tokens, the raw details blob and status are stripped.

curl -u user:app-password https://your-manager.example.com/wp-json/captaincore/v1/sites

[
  {
    "site_id": 135,
    "account_id": 12,
    "customer_id": 12,
    "name": "example.com",
    "site": "example",
    "provider": "kinsta",
    "core": "6.9.1",
    "home_url": "https://example.com",
    "storage": 123456789,
    "visits": 15000,
    "removed": false,
    "environments": [
      { "environment_id": 3365, "environment": "Production", "home_url": "https://example.com", "core": "6.9.1" }
    ]
  }
]

GET /sites/{site_id} accepts either the numeric id or the slug, and the same handler serves both. It is heavier than /details, which is what the site overview screen actually loads.

Creating a site takes a site object with name, site, account_id, provider and at least a Production entry in environments. Optional keys include customer_id, provider_id, provider_site_id and shared_with.

POST /sites/{site_id} merges the keys you send into the stored site details. Non-administrators may only write details.removed: sending true emails a removal request and logs it, false cancels it.

Environments

PUT /sites/{site_id}/settings takes environment (the database name, so Production or Staging) and a value object with updates_enabled, plus optional updates_exclude_themes and updates_exclude_plugins arrays of slugs.

curl -X POST -u user:app-password \
  -H "Content-Type: application/json" \
  -d '{"source_environment_id": 3365, "target_environment_id": 3366}' \
  https://your-manager.example.com/wp-json/captaincore/v1/sites/environments/push

Files

Both viewing and deleting a file are recorded in the activity log with the path and environment.

curl -u user:app-password \
  "https://your-manager.example.com/wp-json/captaincore/v1/environment/3365/files?path=wp-content&action=list"

Site domains

These are hostnames attached to a hosting environment at the provider, not registrar records. For registrar and DNS work see Domains, DNS and accounts.

Admin tools

curl -u user:app-password \
  https://your-manager.example.com/wp-json/captaincore/v1/sites/135/production/magiclogin

Stats

Site analytics come from Fathom. The integration needs a fathom provider row with an api_key credential.

curl -u user:app-password \
  "https://your-manager.example.com/wp-json/captaincore/v1/sites/135/stats?from_at=2026-08-01&to_at=2026-08-31&grouping=day"

Performance

curl -u user:app-password \
  "https://your-manager.example.com/wp-json/captaincore/v1/sites/135/production/performance-monitor?hours=24&format=raw"

Logs

Live logs are read over SSH. Archived logs come from the provider’s rotation, and are on the older singular /site/ prefix.

curl -X POST -u user:app-password \
  -H "Content-Type: application/json" \
  -d '{"file":"error.log","limit":200}' \
  https://your-manager.example.com/wp-json/captaincore/v1/sites/135/production/logs/fetch

Backups, snapshots and captures

Quicksaves, the daily git history of themes, plugins and core, live on their own routes: /quicksaves, /quicksaves/search, /quicksaves/{hash}, /quicksaves/{hash}/changed, /quicksaves/{hash}/filediff, /quicksaves/{hash}/rollback and /quicksaves/{hash}/sandbox-token. They are served straight from the CLI rather than a Manager table.

Filters

Filters answer “which of my sites run this plugin or theme”.

The full route list, including the administrator-only variants, is in the Endpoint index.