Overview
The/beta/deployments API turns 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 recomputes next_run_at whenever the deployment is created, updated, or triggered.
Deployments are scoped to the authenticated user.
This namespace is served by the Allternit API data-plane node (
http://127.0.0.1:8013 on the same machine, or your paired or provisioned node). The hosted Cloud API at https://api.allternit.com does not route it; it relays only agent sessions, canvases, office and beta research/sessions. See Cloud API.Base URL
The deployment object
The run object
Endpoints
List deployments
Query parameters
Response
Create a deployment
Request body
Response
400 Bad Request.
Get a deployment
Response
Update a deployment
Request body
At least one field must be provided.Response
next_run_at is recomputed on every update, even if only status changes.
Delete a deployment
Deleting a deployment cascades to its run history.204 No Content.
List runs
Response
Trigger a run
Manually enqueue a run and advance the deployment’s schedule. This is useful for testing or for forcing an out-of-cycle execution.Response
last_run_at and recomputes next_run_at on the deployment.
Update a run
Report the terminal outcome of a run. Onlysucceeded, failed, and cancelled are accepted.
Request body
Response
deployment.run.updated.