Skip to main content
POST
/
jobs
/
{UUID}
/
clone
cURL
curl --request POST \
  --url https://api.ionq.co/v0.4/jobs/{UUID}/clone \
  --header 'Authorization: <api-key>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "parent": "<string>",
  "name": "<string>",
  "metadata": {},
  "shots": 100,
  "backend": "<string>",
  "session_id": "<string>",
  "settings": {
    "error_mitigation": {
      "debiasing": true
    },
    "compilation": {
      "opt": 123,
      "precision": "<string>"
    }
  },
  "dry_run": true
}
'
{
  "id": "617a1f8b-59d4-435d-aa33-695433d7155e",
  "session_id": null
}
Create a new job that reuses the circuit and workload of an existing job. You can override fields such as name, shots, backend, settings, and metadata in the request body — any field you omit is inherited from the source job. The cloned job is queued as a brand new job, and the original is left unchanged. This is useful for re-running a job with a different number of shots, targeting another backend, or adjusting error mitigation settings without rebuilding the circuit.

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

Path Parameters

​
UUID
string
required

The UUID of the job to clone.

Body

application/json

Make all properties in T optional

​
parent
string
​
name
string
​
metadata
object

User defined metadata

​
shots
integer<int32>
default:100

shots is ignored by ideal simulator backend.

Required range: 1 <= x <= 1000000
​
backend
string
​
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