Projects & Environments | ZopDev Developer Docs

A project groups one or more environments (typically dev, staging, prod) under a shared product or team. An environment binds a project to a deployment space (a registered Kubernetes cluster) and a namespace, plus a registry for pushing built images.

Projects

POST /projects

Create a project.

curl -X POST https://api.zop.dev/projects \
  -H "Authorization: Bearer <token>" \
  -H "Content-Type: application/json" \
  -d '{ "name": "checkout" }'

GET /projects

List projects.

GET /projects/stats

Batch stats (env count, service count, status buckets, last deploy) for every project the caller can see, used to render the dashboard cards in a single round-trip.

GET /projects/{projectID}

Get a single project.

PATCH /projects/{projectID}

Rename a project.

DELETE /projects/{projectID}

Soft-delete a project. All child environments and deployments must be removed first.

Environments

Environments live under a project. Each environment binds:

A deployment space (the registered cluster).
A namespace on that space’s cluster.
An optional registry integration plus URL for built images (typically the cloud account’s native registry. ECR / Artifact Registry / ACR).

POST /projects/{projectID}/environments

Create an environment under a project.

curl -X POST https://api.zop.dev/projects/prj_acme/environments \
  -H "Authorization: Bearer <token>" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "prod-us-east",
    "spaceId": "spc_abc",
    "namespace": "checkout-prod",
    "registryIntegrationId": "int_ecr_001",
    "registryUrl": "123456789012.dkr.ecr.us-east-1.amazonaws.com/checkout"
  }'

GET /projects/{projectID}/environments

List environments under a project.

GET /projects/{projectID}/environments/{envID}

Get an environment in nested-path form (used by the canvas).

PATCH /projects/{projectID}/environments/{envID}

Update an environment (name, space, namespace, registry).

DELETE /projects/{projectID}/environments/{envID}

Soft-delete an environment. All deployments must be removed first.

Flat lookup

For deep-link URLs and integrations that hold an env ID without its project, the catalog exposes a flat lookup:

GET /environments/{envID}

Get an environment by ID without knowing its project.

Live cluster discovery

The endpoint below runs against the environment’s target cluster in real time, using short-lived credentials minted from the cloud account.

GET /environments/{envID}/cluster-discovery

Live cluster discovery: ingress controllers and cert managers actually present on the namespace's cluster. Used to populate the ingress dropdown without showing stale options when an admin removes a controller.

For per-project counts (environments, services, status buckets, last deploy), use GET /projects/stats.

Topology & the Canvas

The Architecture canvas is rendered client-side from the same catalog endpoints above. There is no aggregated server-side topology endpoint on the public API. The client lists projects, environments and deployments, groups them into the project → environment → deployment hierarchy, and places each card using the stored canvasPosition on each deployment.