Skip to main content
GET
Get a job

Authorizations

Authorization
string
header
required

An API key minted in Command Center (Settings -> API Keys), sent as Authorization: Bearer 2501_ak_.... A Command Center session cookie is also accepted.

Path Parameters

id
string
required

Response

The job

id
string
required
Example:

"job_9f3b6d2a-..."

org_id
string
required
ticket_id
string | null
required

The ticket that opened the job; null for a job started another way

gateway_id
string | null
required
job_schedule_id
string | null
required
owner_id
string | null
required

The user who started the job

status
enum<string>
required

completed and failed end a run. Every other value is a step of a run in progress. A job can be reopened, which starts a new run (see reopened_at).

Available options:
pending,
pre_process,
attachment_processing,
task_creation,
task_update,
in_progress,
waiting_for_approval,
failed,
completed,
attachment_processing_failed
Example:

"completed"

execution_mode
enum<string> | null
required

The mode forced on every agent of the job. investigate is Plan; remediate is Auto. null: each agent uses its own mode.

Available options:
investigate,
remediate,
null
Example:

"investigate"

description
string | null
required
resolution_status
enum<string> | null
required
Available options:
hard_failure,
no_action,
success,
agentic_failure,
partial,
null
resolution_reasoning
string | null
required
created_at
string<date-time>
required
Example:

"2026-08-26T10:00:26.380Z"

updated_at
string<date-time>
required
Example:

"2026-08-26T10:00:26.380Z"

completed_at
string<date-time> | null
required
Example:

"2026-08-26T10:00:26.380Z"

reopened_at
string<date-time> | null
required
Example:

"2026-08-26T10:00:26.380Z"

reopen_trigger
enum<string> | null
required

What reopened the job: a mention in the ticket or a ticket state change

Available options:
mention,
ticket_state,
null