Jobs API
Jobs represent asynchronous executions (pathway runs, receptor invocations). Start a run viaPOST /v1/pathways/:id/execute (Pathways) or POST /v1/jobs with { "pathway_id": "<uuid>", "input": { ... } }; both return job_id. Then poll GET /v1/jobs/:jobId/status or consume GET /v1/jobs/:jobId/stream (SSE).
Start pathway run
pathway_id (required for stored pathway) or inline pathway, optional input or signal. Response: { "job_id": "...", "status": "pending" }.
List jobs
pathway_id, receptor_id, status, limit, offset. Response: { "jobs": [...], "total", "limit", "offset" }. Workspace-scoped.
Get job status
current_step, failedReason, result (when completed), waitingFor (when paused for input). Status is authoritative from BullMQ; an optional Redis key may be used internally for early “queued” visibility.
Response fields: job_id, status (pending | running | completed | failed | waiting | paused), progress, current_step, failedReason, result, waitingFor, created_at, processed_at, finished_at.
- TypeScript
- curl
Stream job progress
complete or error). Same workspace check as status.
Cancel job
Resume job
waiting or paused (e.g. human node).
Submit input (waiting job)
{ "input": { ... } }. Use when a run is waiting for user input; then resume.
Transcribe audio
job_id.
auvy.jobs.transcribe(file) in the TypeScript SDK or the public receptor transcription route when you need share-token access.
Related
- Pathways API — Execute pathway by ID or via POST /v1/jobs
- Receptors API — Invoke by receptor (returns job_id)
- Public Endpoints — Shared receptor execution and transcription
- Integration patterns — Error patterns