Overview
The Beta Deployments API lets you turn an agent into a scheduled service. A deployment binds an agent to a cron expression and tracks every execution in a separate run history. The scheduler recomputesnext_run_at whenever a deployment is created, updated, or triggered.
All deployment routes are mounted under /api/v1/beta/deployments and require a valid bearer token via the platform auth middleware.
Base URL
Authentication
All requests must include a valid bearer token in theAuthorization header. See Authentication for details.
Deployment object
Run object
Endpoints
List deployments
Query parameters
Example request
Example response
Create a deployment
active and next_run_at is computed from the provided cron expression.
Request body
Example request
Example response
Get a deployment
Example request
Example response
Update a deployment
COALESCE semantics: omitted fields keep their current values. At least one field must be provided. The next_run_at field is recomputed on every update, even if only status changes.
Request body
Example request
Example response
Delete a deployment
Example request
204 No Content with no response body.
List runs
Example request
Example response
Trigger a run
running, and the deployment’s last_run_at and next_run_at are updated.
Example request
Example response
Update a run
succeeded, failed, or cancelled.
Request body
Example request
Example response
deployment.run.updated. See Webhooks for details.