SnozeDevelopers
API referenceAutomations

List automation runs across the whole workspace

Returns runs for every automation in the workspace in one stream, newest first, for the workspace runs page. Requires the `automations:read` permission. Narrow the result with a comma-separated `statuses` list and page by passing `beforeStartedAt` and `beforeId` from the last row of the previous page; an unrecognized status, or one cursor field without the other, is rejected as a query validation error.

GET
/v1/workspaces/{workspaceId}/automation-runs

Authorization

apiKey
headerAuthorizationBearer <snoze_sk_…>

Workspace API key created in Workspace settings → API keys. Scopes on the key bound what it can read and write.

Path Parameters

workspaceId*string

Query Parameters

limit?string|null
statuses?string|null
query?string|null
beforeStartedAt?string|null
beforeId?string|null

Response Body

Success

application/json
  1. response
data*array<>
hasMore*boolean
nextCursor?|null
Example Request
curl -X GET 'https://api.snoze.dev/v1/workspaces/string/automation-runs'
Example Response
{  "data": [    {      "id": "string",      "workspaceId": "string",      "automationId": "string",      "automationLabel": "string",      "automationKey": "string",      "status": "queued",      "source": "manual",      "startedAt": "string",      "completedAt": "string",      "error": "string"    }  ],  "hasMore": true,  "nextCursor": {    "startedAt": "string",    "id": "string"  }}

List an automation's runs

Returns the automation's runs, newest first, each expanded with its per-node executions. Requires the `automations:read` permission plus view access to the automation. Pass `limit` to change the page size; it defaults to 30 and is capped at 100.

Publish an automation's draft version

Promotes the current draft to the published version and installs its triggers, optionally enabling the automation or rotating its webhook signing secret at the same time. Requires the `automations:write` permission plus edit access; the draft is recompiled under stricter publish-time rules, so an automation with no unpublished changes, no steps, or an invalid graph is rejected with a validation error. Send an `Idempotency-Key` header to make retries safe; a replay within the window returns the original response.