Skip to main content
POST
/
jobs
curl -X POST "https://api.ionq.co/v0.4/jobs" \
  -H "Authorization: apiKey your-api-key" \
  -H "Content-Type: application/json" \
  -d '{
    "type" : "ionq.circuit.v1",
    "name": "Sample circuit",
    "metadata": {
      "fizz": "buzz",
      "foo": "bar"
    },
    "shots": 500,
    "backend": "qpu.forte-1",
    "settings" :
    {
      "error_mitigation":
      {
        "debiasing": false
      }
    },
    "input": {
      "qubits":  2,
      "gateset": "qis",
      "circuit": [
      {
        "gate": "h",
        "target": 0
      }
      ]
    }
  }'
{
  "id": "617a1f8b-59d4-435d-aa33-695433d7155e",
  "status": "submitted",
  "session_id": null
}

Documentation Index

Fetch the complete documentation index at: https://docs.ionq.com/llms.txt

Use this file to discover all available pages before exploring further.

Submit a quantum circuit to run on a backend by creating a new job. You can specify the number of shots, target backend (QPU or simulator), and optional settings like error mitigation. The job will be queued and executed according to the platform’s scheduling system. Learn more about submitting circuits via API.

Authorizations

​
Authorization
string
header
required

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

Body

application/json
​
backend
string
required

Available options: simulator, qpu.aria-1, qpu.aria-2, qpu.forte-1, qpu.forte-enterprise-1

​
type
enum<string>
required
Available options:
ionq.circuit.v1
​
input
Qis Circuit · object
required
​
name
string
​
metadata
object

User defined metadata

​
shots
integer<int32>
default:100
Required range: x <= 1000000
​
session_id
string
​
settings
object
​
dry_run
boolean
​
noise
object

Response

Created

​
id
string
required
Example:

"617a1f8b-59d4-435d-aa33-695433d7155e"

​
status
enum<string>
required
Available options:
submitted,
ready,
started,
canceled,
failed,
completed
​
session_id
string | null
required
Example:

null