Fetch a job’s status envelope. Poll until status transitions
to completed or failed, then fetch /v1/jobs/{id}/results
to read the typed output.
Suggested polling cadence: humanization 3 s, structure 10 s, stability
and immunogenicity 10 s. Polling is a read and does not burn
the monthly write quota, but it does consume the per-minute rate
bucket — stagger bursts of polls across many jobs to stay under
X-RateLimit-Remaining.
Cost: read — rate bucket only.
.. deprecated::
Use the typed resource endpoints instead (e.g. GET /v1/humanizations/{id}).
This endpoint will be removed in /v2.
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Successful Response
A pipeline job's status envelope.
Opaque job identifier (UUID).
"dddd1111-eeee-2222-ffff-333344445555"
Variant this job is running against.
"11112222-3333-4444-5555-666677778888"
One of: humanization, structure, stability, immunogenicity.
"humanization"
One of: pending, running, completed, failed.
"pending"
ISO-8601 timestamp when the job was submitted.
"2026-04-21T14:15:00+00:00"
ISO-8601 timestamp when execution started. null while pending.
"2026-04-21T14:15:02+00:00"
ISO-8601 timestamp when execution finished. null until completed or failed.
null
Human-readable failure reason. Populated only when status=failed.
null