Skip to main content
A deployment fires an agent on a schedule without a human at the terminal. Nine methods. API detail: Deployments.

create

POST /v1/deployments. Requires agent_id, cron, and input_template; the rest of the deployment config is optional. agent_version pins the exact version this cron fires; timezone reads the cron expression.

list

GET /v1/deployments, cursor-paginated.

get

GET /v1/deployments/{id}.

update

PATCH /v1/deployments/{id}. DeploymentPatch is every config field optional except agent_id, which cannot be changed — repoint by creating a new deployment.

run

POST /v1/deployments/{id}/run. Fire once, now — the “run it and see” verb. Does not touch the schedule.

runs

GET /v1/deployments/{id}/runs — the history, each run pointing at the session it started.

pause / resume

POST /v1/deployments/{id}/pause and POST /v1/deployments/{id}/resume. Pausing stops the schedule; run still works while paused.

delete

DELETE /v1/deployments/{id}. Past runs and their sessions remain readable.