See what’s new in API v0.4 and how to migrate from v0.3.
This guide covers the key changes when upgrading from IonQ’s API v0.3 to v0.4. The new version introduces several structural improvements and new features while maintaining compatibility for most existing workflows.
output
field to calling GET /jobs/{UUID}/results/probabilities
/backends/
results.probabilities.url
fieldJob results are now organized into dedicated sub-endpoints with results.probabilities.url
field instead of direct output
field, requiring updates to result retrieval logic to use the new GET /jobs/{UUID}/results/probabilities
endpoint.
v0.3: Job results included directly in job response with output
field
v0.4: Results moved to dedicated endpoint structure with results.probabilities.url
field
v0.4 introduces GET /jobs/{UUID}/cost
for retrieving detailed billing information including estimated and actual costs in USD, enabling better cost tracking and budget management at the job level.
Job responses now include additional fields: child_job_ids
, session_id
, and timing prediction fields for improved job monitoring and workflow management.
GET /jobs/{UUID}/output
→ GET /jobs/{UUID}/results/probabilities
Characterizations now use a more intuitive REST structure with endpoints nested under backends and pagination support.
v0.3 Endpoints:
GET /characterizations/{backend}/all
GET /characterizations/{backend}/current
GET /characterizations/{characterization_id}
v0.4 Endpoints:
GET /backends/{backend}/characterizations
(with pagination)GET /backends/{backend}/characterizations/{characterization_id}
GET /backends/{backend}
(individual backend details)Backend responses now include degraded
status flag and characterization_id
linking for better backend selection and status monitoring capabilities.
Characterization filtering now uses ISO date strings (e.g., start=2025-12-31
) instead of Unix timestamps (e.g., start=1585713600000
).
Characterization endpoints now include limit
and page
parameters for improved pagination control alongside the updated date string format.
See what’s new in API v0.4 and how to migrate from v0.3.
This guide covers the key changes when upgrading from IonQ’s API v0.3 to v0.4. The new version introduces several structural improvements and new features while maintaining compatibility for most existing workflows.
output
field to calling GET /jobs/{UUID}/results/probabilities
/backends/
results.probabilities.url
fieldJob results are now organized into dedicated sub-endpoints with results.probabilities.url
field instead of direct output
field, requiring updates to result retrieval logic to use the new GET /jobs/{UUID}/results/probabilities
endpoint.
v0.3: Job results included directly in job response with output
field
v0.4: Results moved to dedicated endpoint structure with results.probabilities.url
field
v0.4 introduces GET /jobs/{UUID}/cost
for retrieving detailed billing information including estimated and actual costs in USD, enabling better cost tracking and budget management at the job level.
Job responses now include additional fields: child_job_ids
, session_id
, and timing prediction fields for improved job monitoring and workflow management.
GET /jobs/{UUID}/output
→ GET /jobs/{UUID}/results/probabilities
Characterizations now use a more intuitive REST structure with endpoints nested under backends and pagination support.
v0.3 Endpoints:
GET /characterizations/{backend}/all
GET /characterizations/{backend}/current
GET /characterizations/{characterization_id}
v0.4 Endpoints:
GET /backends/{backend}/characterizations
(with pagination)GET /backends/{backend}/characterizations/{characterization_id}
GET /backends/{backend}
(individual backend details)Backend responses now include degraded
status flag and characterization_id
linking for better backend selection and status monitoring capabilities.
Characterization filtering now uses ISO date strings (e.g., start=2025-12-31
) instead of Unix timestamps (e.g., start=1585713600000
).
Characterization endpoints now include limit
and page
parameters for improved pagination control alongside the updated date string format.