Skip to main content
GET
/
jobs
/
{job_id}
Get Job
curl --request GET \
  --url https://trio.machinefi.com/api/jobs/{job_id} \
  --header 'Authorization: Bearer <token>'
{
  "job_id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
  "status": "pending",
  "job_type": "<string>",
  "created_at": "<string>",
  "stream_url": "<string>",
  "config": {},
  "stats": {}
}
Returns runtime state for a single async job. This is the primary endpoint for polling monitor/digest jobs and interpreting final outcomes.

​
Response Semantics

The response separates data into:
  • config: user-supplied job settings
  • stats: runtime progress and result fields
stats can evolve while a job is running.

​
Status Semantics

Possible status values:
  • pending: accepted, not yet running
  • running: actively processing
  • completed: finished successfully
  • stopped: ended without failure
  • failed: ended due to runtime/stream failure
Recommended client handling:
  • completed: consume final result fields
  • stopped: inspect stop reason and restart if needed
  • failed: inspect error context, fix inputs, retry

​
Common Uses

  • Poll live-monitor / live-digest in polling mode
  • Validate final outcomes after webhook/SSE flows
  • Inspect stop reasons and counters during debugging

​
Workflow

  1. Create a job with Live Monitor or Live Digest
  2. Poll GET /jobs/{job_id} until terminal status
  3. Cancel early via Cancel Job if needed

Authorizations

​
Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

​
job_id
string<uuid>
required

Response

Successful Response

Detailed response for a single job with config/stats split.

​
job_id
string<uuid>
required
​
status
enum<string>
required

Job status enum.

Available options:
pending,
running,
stopped,
completed,
failed
​
job_type
string
required
​
created_at
string
required
​
stream_url
string
required
​
config
Config · object
​
stats
Stats · object