List cron schedules
const url = 'https://example.com/v1/schedules?limit=25&status=active';const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url 'https://example.com/v1/schedules?limit=25&status=active' \ --header 'Authorization: Bearer <token>'Cursor-paginated. Tombstoned rows excluded. Optional ?status=active|paused filter.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Query Parameters
Section titled “Query Parameters”1..100. Default 25.
Opaque cursor from a prior response. Absent → first page.
Lifecycle status. Only active triggers fire. Tombstoned rows are excluded from every read path.
Filter to triggers at a specific status. Values: active | paused.
Responses
Section titled “Responses”Page of schedules.
object
object
Domain-friendly alias for triggerId — the trigger id (a UUID). Use interchangeably in admin URLs.
5- or 6-field cron expression (croner-compatible). 6-field enables second precision.
IANA timezone (e.g. UTC, America/New_York). Absent → UTC.
Static input handed to the flow on every fire. Absent → {}.
Lifecycle status. Only active triggers fire. Tombstoned rows are excluded from every read path.
Wall-clock time of the next scheduled fire. null on paused rows if the cron scheduler never re-armed.
Example
{ "data": [ { "status": "active" } ]}Missing / malformed / expired / revoked bearer token.
object
object
Stable machine-readable discriminant. Values match domain error codes (see docs/API-ROUTE-CONVENTIONS.md §4.3).
Optional, kind-specific.
object
Server-assigned request id; also echoed via X-Request-Id header.
Examplegenerated
{ "error": { "code": "example", "message": "example", "details": {}, "requestId": "example" }}