Skip to main content
When a job completes, its results object contains one entry per available result artifact, keyed by format identifier. Each entry is an ArtifactDescriptor — pass the descriptor’s id to the artifact endpoint to download the payload. To fetch the JSON Schema for a format, call GET /v0.4/schemas/formats/{format} with the identifier.

Catalog of supported result artifact formats. Each property below documents one format's payload structure. Used by the Results formats docs page.

ionq.result.probabilities.json.v1
object
required

ionq.result.probabilities.json.v1 — Legacy probability distribution. Flat object keyed by decimal qubit state integer strings, values are probabilities summing to 1.

Example:
ionq.result.probabilities.json.v2
object
required

ionq.result.probabilities.json.v2 — Register-nested probability distribution. Each register maps zero-padded bitstrings to probabilities summing to 1 within the register.

Example:
ionq.result.histogram.json.v1
object
required

ionq.result.histogram.json.v1 — Legacy shot count histogram. Flat object keyed by decimal qubit state integer strings, values are shot counts.

Example:
ionq.result.histogram.json.v2
object
required

ionq.result.histogram.json.v2 — Register-nested shot count histogram. Each register maps zero-padded bitstrings to shot counts.

Example:
ionq.result.shots.json.v1
string[]
required

ionq.result.shots.json.v1 — Legacy per-shot outcomes. Array of decimal qubit state integer strings, one element per shot.

Example:
ionq.result.shots.json.v2
object
required

ionq.result.shots.json.v2 — Per-shot register outcomes. Each shot records measured bit arrays for every named register.

Example:
ionq.result.probabilities-aggregate.json.v1
object
required

ionq.result.probabilities-aggregate.json.v1 — Aggregated probability distributions across all circuits in an ionq.multi-circuit.v1 job. Top-level keys are child job UUIDs; each value is that child's probability distribution.

Example: