Supervisor API
This article and the rest of the API documentation in this section are written for a technical audience — integrators and developers connecting external systems to Tickiti. Familiarity with HTTP, REST, JSON and bearer-token authentication is assumed.
The Supervisor API exposes the Supervisor screens — the job queue, health monitoring, scheduled-task configuration and diagnostics. Every endpoint runs as the token’s owner and is gated by the supervisor ability plus the owner’s superuser role — the most restrictive family.
Abilities and conventions
supervisor:read— read endpoints.supervisor:write— job retry/delete and health configuration. Write implies read.
All endpoints are POST and JSON. Job retry/delete keep the server-side guard that never touches the portal_default queue.
Endpoints
| Method & path | Ability | Purpose |
|---|---|---|
| POST /api/v1/supervisor/jobs | supervisor:read | List queued + failed jobs |
| POST /api/v1/supervisor/jobs/retry | supervisor:write | Retry failed jobs (job_ids) |
| POST /api/v1/supervisor/jobs/delete | supervisor:write | Delete failed jobs (job_ids) |
| POST /api/v1/supervisor/health | supervisor:read | System health status |
| POST /api/v1/supervisor/health/manage | supervisor:read | Disk thresholds + ignore patterns |
| POST /api/v1/supervisor/health/disk/store | supervisor:write | Create/update a disk threshold |
| POST /api/v1/supervisor/health/disk/delete | supervisor:write | Delete a disk threshold by id |
| POST /api/v1/supervisor/health/exception/store | supervisor:write | Create/update a failed-job ignore pattern |
| POST /api/v1/supervisor/health/exception/delete | supervisor:write | Delete an ignore pattern by id |
| POST /api/v1/supervisor/super-tasks | supervisor:read | Read scheduled tasks / settings / templates |
| POST /api/v1/supervisor/diagnostics | supervisor:read | Diagnostic-related option flags |
Not exposed
Creating, updating or deleting super-tasks is deliberately not available over the API: a task stores an arbitrary program the scheduler executes, so writing one through a long-lived token would be a remote-code-execution path. Manage scheduled tasks from the Supervisor UI. The read endpoint above is provided for monitoring.