Update an automation's status

Changes an automation's lifecycle status. Allowed transitions: ACTIVE → INACTIVE, INACTIVE → ACTIVE, INACTIVE → DISABLED; DISABLED is terminal. Any other transition is rejected with 400, including setting the status the automation already holds. The change is recorded in the automation's history.

A TIME automation is registered with the scheduler when it becomes ACTIVE and unregistered on every other target status.

A soft-deleted automation is still resolved, so a transition away from DELETED is rejected with 400. DELETED is reached through DELETE /api/automations/{automationId}, not through this endpoint.

Path Params
uuid
required

Id of the automation.

Body Params
string
enum
required

Target lifecycle status. Allowed transitions: ACTIVE→INACTIVE, INACTIVE→ACTIVE, INACTIVE→DISABLED. DISABLED is terminal; any other transition is rejected with 400.

Allowed:
Headers
string
^\d+\.\d+\.\d+$

Version of the API contract the client targets, in MAJOR.MINOR.PATCH format. Mandated by the Gateway standard. Not yet enforced: requests without the header, or with an unsupported value, are currently processed normally. Once enforcement is enabled, such requests will be rejected with 400 Bad Request.

string
required
length ≥ 1

Required on every POST, PUT and PATCH. A client-generated key: retrying with the same key returns the original response without running the request again. Scoped per tenant, user, method and path. A missing or blank key is rejected with 400.

Responses

Language
Credentials
Bearer
JWT
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json