Schedules API
GET /api/v1/schedules?project_id=...&scheduler=celery-beatResponse:
{ "items": [ { "id": "...", "scheduler": "celery-beat", "name": "nightly-digest", "task": "emails.send_digest", "cron": "0 3 * * *", "args": [], "kwargs": {"variant": "full"}, "enabled": true, "last_run_at": "...", "next_run_at": "..." } ], "next_cursor": null, "has_more": false}Create
Section titled “Create”POST /api/v1/schedulesRole: admin. Body:
{ "project_id": "...", "scheduler": "celery-beat", "name": "nightly-digest", "task": "emails.send_digest", "cron": "0 3 * * *", "kwargs": {"variant": "full"}, "enabled": true}Returns 201 Created with the new schedule. Returns 409 if scheduler is read-only.
Update
Section titled “Update”PATCH /api/v1/schedules/{id}Any subset of fields. Role: admin.
Pause / Resume
Section titled “Pause / Resume”POST /api/v1/schedules/{id}/pausePOST /api/v1/schedules/{id}/resumeRole: admin.
Delete
Section titled “Delete”DELETE /api/v1/schedules/{id}Role: admin. Returns 204 No Content.
Readability / writability per scheduler
Section titled “Readability / writability per scheduler”See schedulers overview for the full matrix. Read-only schedulers return 409 scheduler_read_only on write operations.