Join our Slack

Example Notebooks

Other Resources

IonQ Quantum Cloud Documentation

Home

SDKs

API Reference

Sign In

**NOTE**: If request filters are provided, this endpoint will limit responses to 1 or more specific jobs based on those filters.<br /><br />
This endpoint retrieves all jobs this API key is authorized to view.


Get Jobs

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.

Set to true to turn on [debiasing](https://ionq.com/resources/debiasing-and-sharpening), which can improve circuit performance by removing qubit-specific noise. _Debiasing is on by default for Aria-class systems._

A list of child jobs that were created from this job.

The predicted execution time of this job.

The point in time this job was requested.

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.

Warning metadata, if a warning is necessary.

The UUID of a job. We'll provide the UUID initially in our response to a [job creation request](#operation/createJob).

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.)

Selects a noise model to apply to a simulation job. The default, `ideal`, provides perfect simulation without noise, while other noise models like `harmony` are based on noise data collected from our actual quantum computers. Note that these are simplified noise models, not intended to exactly reproduce real quantum computations.

This is the seed value for the pseudo-random sampling and noise generation when a system noise model is specified. The seed needs to be a positive integer between 1 and 2^31. Providing a seed is optional and allows for repeatable (i.e. non-random) outcomes. If a seed is not specified, one is chosen at random and will be provided in the output for the simulation. This field does not apply to simulations using the "ideal" noise model. This field also does not apply to `qpu.*` targets.

How many times to execute your circuit when submitting to a QPU or a "non-ideal" noisy simulator.

API Key

Response body when requesting all or many jobs.

Learn how to create and manage your IonQ API keys for secure access through SDKs and APIs.

Managing API keys

Learn how to submit jobs directly to the IonQ API

Direct API Submissions

Things to do before submitting to IonQ's hardware systems.

QPU Submission Checklist

Getting started with hardware noise model simulation

Simulation with Noise Models

Getting started with IonQ's hardware-native gateset

Native Gates

Run hybrid execution loops using functions managed by IonQ's Cloud.

Hosted Hybrid Service

SDKs allow access to IonQ resources directly from within your code environment

Overview

Quantum SDKs

Learn how to use the Qiskit SDK to submit quantum circuits to IonQ's simulators and quantum computers.

Getting started with Qiskit

Learn how to use IonQ's error mitigation techniques with Qiskit

Using debiasing with Qiskit

Learn how to use our hardware-native gateset to run a circuit with Qiskit

Using native gates with Qiskit

Learn how to use the Cirq SDK to submit quantum circuits to IonQ's simulators and quantum computers.

Getting started with Cirq

Learn how to use our hardware-native gateset to run a circuit with Cirq

Using native gates with Cirq

Learn how to use PennyLane to submit quantum circuits to IonQ's simulators and quantum computers.

PennyLane

Learn how to use our hardware-native gateset to run a circuit with PennyLane

Using native gates with PennyLane

Learn how to use TensorFlow Quantum to connect your ML workflows to IonQ's simulators and quantum computers.

TensorFlow Quantum

Your Account

Jobs are tasks running on IonQ systems, usually containing a circuit to run on a QPU.

Jobs

Organizations

Projects are collaborative workspaces created in an organization to manage teams and resources.

Projects

An overview of some of the systems that make up the IonQ Quantum Cloud Platform

Platform Systems

Glossary

Learn how to connect to IonQ products and services through AWS Braket

Amazon Braket

Enhance security and simplify user management by authenticating with your SAML-based SSO provider

Connecting a SAML Identity Provider

Introduction

API Core Concepts

v0.3 Error Codes

Writing Quantum Programs

Migrating from old versions

This guide covers everything from setting up a multicircuit job, submitting it to IonQ's backend, and retrieving the results.

Multicircuit Jobs

Learn how to use our hardware-native gateset to run a circuit with the IonQ API

Using native gates with the IonQ API

To submit a program to be simulated or executed on our quantum hardware, `POST` it to the `jobs` endpoint.

Create a Job

Permanently remove many jobs from our platform. This cannot be undone.

Delete many Jobs

Get a specific Job

Permanently delete a job from our service. This cannot be undone.

Delete a Job

Retrieve a specific job's results by UUID.

Get a Job's output

Cancel the execution of a single job by ID.

Cancel a Job

Cancel the execution of many jobs at once by passing a list of jobs.

Cancel many Jobs

This endpoint retrieves an array of all available backend characterizations, with pagination.

Get All Backend Characterizations

This endpoint retrieves the most recent backend characterization data available.

Get the Most Recent Backend Characterization

This endpoint retrieves a characterization.

Get a Characterization

Retrieve a list of all available backends.

Get Backends

Get a usage report for the given organization from the start_date and end_date, detailing how much usage went to each QPU during that period. If no start_date or end_date are provided, period defaults to last 30 days until current time.

IonQ APIs

Jobs

Characterizations

Backends

Reports

Get Jobs

Authorizations

Query Parameters

Response