Please add public REST endpoints under api.wpengineapi.com/v1/ for Atlas / Headless apps so we can list builds for an environment and fetch a single build's status — using the existing Hosting Platform API user/password we already use for /installs, /sites, etc. Suggested shape: GET /v1/headless/applications/{app_id}/environments/{env_id}/builds (list) GET /v1/headless/applications/{app_id}/environments/{env_id}/builds/{build_id} (single) Response should include at minimum: id, state (queued/building/succeeded/failed), started_at, finished_at, and a last log line or failure reason. Why it matters: the Build Hook URL already lets us trigger a build from anywhere (WP admin, CMS, scripts). But once triggered, there is no way to programmatically know what happened without scraping the portal. We're building an in-WordPress "Rebuild" button so non-technical editors can see live build status without leaving WP. Today it has to fall back to "status unknown" because no public endpoint exists. The CLI (wpe builds get / wpe builds list) clearly has access to this data — please surface the same data over the public REST API. This unblocks a real workflow for our content team and likely many other Atlas customers building admin integrations. — TRG International (trgprodcms)
