Get Job Results And Status

curl --request GET \
  --url 'https://api.example.com/ai/jobs/{job_id}/results?HAIQU_API_KEY='

{
  "id": "<string>",
  "user_id": 123,
  "experiment_id": "<string>",
  "creation_date": "2023-11-07T05:31:56Z",
  "context": "<string>",
  "name": "<string>",
  "description": "<string>",
  "device_id": "Haiqu OS",
  "run_date": "2023-11-07T05:31:56Z",
  "finish_date": "2023-11-07T05:31:56Z",
  "logs": "<string>",
  "quality": 123,
  "info": {},
  "time": 123,
  "parameters": {}
}

API Reference

Get Job Results And Status

Get current status and result payload for a submitted job.

Use this tool after any asynchronous MCP submit endpoint returns a job_id and the caller needs current state or terminal results. When the job is still running, the response remains the full job object plus MCP context, not a polling-only acknowledgment.

When to Use:

Call this after any asynchronous MCP submit endpoint returns a job_id.
Call this when the workflow needs current status, terminal outputs, or the MCP context summary for a known job.

Constraints:

This route is for status lookup, not discovery.
Result shape depends on job family. For example, non-dry run RunJob responses may surface raw quantum_results in the MCP context field instead of a textual summary.

Notes:

If the caller does not yet know the job ID, use experiment or circuit job-listing tools first.
Compression, transpilation, data-loading, analytics, and run jobs can all appear here with different result semantics.

Args: job_id: Job identifier returned by a prior MCP submission or listing endpoint. user: Authenticated user resolved from the API key. db: Active database session.

Returns: The resolved job object enriched with MCP context text or result data.

Raises: HTTPException: Raised with 404 when the job cannot be found for the caller scope.

GET

/

ai

/

jobs

/

{job_id}

/

results

Get Job Results And Status

curl --request GET \
  --url 'https://api.example.com/ai/jobs/{job_id}/results?HAIQU_API_KEY='

{
  "id": "<string>",
  "user_id": 123,
  "experiment_id": "<string>",
  "creation_date": "2023-11-07T05:31:56Z",
  "context": "<string>",
  "name": "<string>",
  "description": "<string>",
  "device_id": "Haiqu OS",
  "run_date": "2023-11-07T05:31:56Z",
  "finish_date": "2023-11-07T05:31:56Z",
  "logs": "<string>",
  "quality": 123,
  "info": {},
  "time": 123,
  "parameters": {}
}

Authorizations

HAIQU_API_KEY

string

query

required

Path Parameters

job_id

string

required

Response

Successful Response

Extend base job model with MCP context payload.

Attributes: context: context string or raw result list, depending on job family and status.

id

string

required

user_id

integer

required

experiment_id

string

required

status

enum<string>

required

Class for job status.

Available options:

Submitted,

Initializing,

Queued,

Validating,

Running,

Cancelled,

Done,

Error

job_type

enum<string>

required

Class for job types.

Available options:

User local job,

Analytics,

Device specific analytics,

Data Loading,

Run,

State Compression,

Transpilation,

Variational,

Pretraining,

SKQD

creation_date

string<date-time>

required

context

required

context string or raw result list, depending on job family and status. Run jobs may return raw quantum_results here.

name

string | null

description

string | null

device_id

string | null

default:Haiqu OS

run_date

string<date-time> | null

finish_date

string<date-time> | null

logs

string | null

quality

number | null

info

Info · object

time

number | null

parameters

Transpile Circuits List Qpus And Simulators

⌘I