Skip to main content
GET
Get ingest job status
Scoped to the effective subject and the caller’s org; a job belonging to anyone else returns 404 rather than leaking its status.

Authorization

This route requires the read scope. A missing or invalid credential returns 401 authentication_error. A valid credential without the scope returns 403 permission_denied, and the problem body names the exact scope required.

Headers

These are request conventions the contract does not declare as parameters, so they do not appear in the schema tables below.

Success responses

Errors

Every error is an RFC 9457 application/problem+json body carrying a stable code, a requestId, and a suggestedAction where Exo has one. See Errors.

Notes

  • A job that is not yours is 404, not 403. Status cannot be probed across subjects or organizations.

Authorizations

X-Exo-API-Key
string
header
required

An Exo API key (exo_...) sent as the X-Exo-API-Key header.

Path Parameters

job_id
string<uuid>
required

Response

The job's status and progress.

jobId
string
required
status
string
required
completedSteps
string[]
errorMessage
string | null
percent
integer
default:0
phase
string | null