Get a specific Job
Retrieve a specific job by UUID.
Authorizations
API keys are associated with a user and can be created on the
IonQ Quantum Cloud application. To authenticate, prefix your API Key with apiKey
and place it in the Authorization
request header. Ex: Authorization: apiKey your-api-key
Path Parameters
The UUID of the job — this UUID is provided in the response on job creation.
Query Parameters
Exclude certain fields from the response (e.g., exclude=status,device_id
).
Only return the provided fields (e.g., include=status,device_id
).
Response
A quantum job.
The UUID of a job. We'll provide the UUID initially in our response to a job creation request.
The point in time this job was requested.
Status of a job.
submitted
, ready
, running
, canceled
, completed
, failed
A list of child jobs that were created from this job.
The number of circuits of this job.
The cost (in US dollars) of this job.
Which error mitigation methods to apply to this circuit. This may affect how the job is compiled, and what configuration can be used to fetch results.
The actual execution time of this job.
Error metadata, if the job failed.
The number of gates used with this job.
User defined metadata.
A job name.
When the target is "simulator", this field specifies optional noise parameters for simulation. (If these noise parameters are not provided, simulations will run on an ideal quantum computer model, without noise.) This field does not apply to qpu.*
targets. When a noise model is applied, the simulator qubit limit is inherited from the modeled QPU's qubit limit. (This limit does not apply to the ideal quantum computer simulator. Please refer to the current qubit limit of the ideal quantum computer simulator.)
The predicted execution time of this job.
The number of qubits used with this job.
The point in time this job was completed.
Relative API path to retrieve the results for this job. See <a href="#tag/jobs/operation/getJobResults">Get a Specific Job's Output</a> for more details.
How many times to execute your circuit when submitting to a QPU or a "non-ideal" noisy simulator.
The point in time this job was started.
Target hardware for job to run on.
qpu.harmony
, qpu.aria-1
, qpu.aria-2
, qpu.forte-1
, simulator
Warning metadata, if a warning is necessary.
Was this page helpful?