Skip to main content
POST
cURL
Move a job by cloning it and canceling the source in a single request. The new job reuses the original circuit and workload, and any fields you provide in the request body — such as name, shots, backend, settings, or metadata — override the inherited values. The cloned job records the source job’s id under metadata.original_job_id. Use this to re-target or re-configure a queued job without leaving the original consuming a queue position. If the source job cannot be canceled — for example because it has already completed — the request fails with a 409 Conflict and no new job is created.

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

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