ionq-core
A client library for accessing IonQ Cloud Platform API.
ionq-core is a typed, async-capable Python client for the IonQ Cloud Platform REST API. The HTTP layer is generated from IonQ's OpenAPI specification with openapi-python-client; a small set of hand-written extensions wraps it with retries, polling, pagination, structured exceptions, and an extension API for downstream SDKs.
The full API reference is published at ionq.github.io/ionq-core.
Looking for a higher-level interface?
ionq-core is the low-level HTTP client. Most users should pick the integration that matches their existing stack:
- Qiskit users ->
qiskit-ionq - Cirq users ->
cirq-ionq - PennyLane users ->
pennylane-ionq - CUDA-Q users -> IonQ is configured as a backend in NVIDIA CUDA-Q.
- Multi-vendor users -> IonQ is reachable via
qbraid.
Use this package directly if you want programmatic access to the IonQ REST API close to the wire, or if you are building a downstream SDK on top of it.
Installation
pip install ionq-core
Quickstart
Submit a Bell-state circuit on the cloud simulator and read the result probabilities:
from ionq_core import IonQClient, wait_for_job
from ionq_core.api.default import create_job, get_job_probabilities
from ionq_core.models.circuit_job_creation_payload import CircuitJobCreationPayload
client = IonQClient() # reads IONQ_API_KEY from the environment
body = CircuitJobCreationPayload.from_dict(
{
"type": "ionq.circuit.v1",
"backend": "simulator",
"shots": 100,
"input": {
"gateset": "qis",
"qubits": 2,
"circuit": [
{"gate": "h", "target": 0},
{"gate": "cnot", "control": 0, "target": 1},
],
},
}
)
job = create_job.sync(client=client, body=body)
completed = wait_for_job(client, job.id)
probs = get_job_probabilities.sync(uuid=job.id, client=client)
print(probs.additional_properties)
Each generated endpoint module exposes four callables: sync, sync_detailed, asyncio, and asyncio_detailed. The sync and asyncio variants return the parsed body; the _detailed variants return a Response[T] with the status code, headers, and parsed body.
For options (api_key, base_url, max_retries, timeout, extension), error classes, retry behavior, pagination, polling, sessions, and downstream-SDK extension hooks, see the API reference.
Versioning
This package follows SemVer 2.0, independent of the upstream REST API version - pass an explicit base_url to IonQClient to pin against a different API. Print the installed version with:
import ionq_core
print(ionq_core.__version__)
The full release history is in CHANGELOG.md.
Contributing
Most of ionq_core/ is generated from the OpenAPI spec and overwritten on every regeneration. See CONTRIBUTING.md for the boundary between generated and hand-written code, development setup, and the regeneration command.
Support
- Bug reports and feature requests: GitHub Issues
- Security disclosures: see SECURITY.md
- Account, billing, or hardware-access questions: ionq.com/contact
License
Apache License 2.0. See LICENSE.
Metadata
Release files for ionq-core 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| ionq_core-0.2.0.tar.gz | 202.2 kB | With provenance | Details for ionq_core-0.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ionq_core-0.2.0-py3-none-any.whl | Python 3 | none | any | Details for ionq_core-0.2.0-py3-none-any.whl |
Total release size: 434.7 kB
Release files / ionq_core-0.2.0.tar.gz
| Download URL | ionq_core-0.2.0.tar.gz |
|---|---|
| Size | 202.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ce5fe16963f696281bb2ffe8723605ee3890f324675137e86967123bfe5dbee3
|
|
BLAKE2b-256 checksum How to use checksums |
b9cd71f2ab2aabdba263798eb62d444c06ba17575b0ded4722a147bbb33b3373
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 19, 2026.
Transparency logRelease files / ionq_core-0.2.0-py3-none-any.whl
| Download URL | ionq_core-0.2.0-py3-none-any.whl |
|---|---|
| Size | 232.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ad3e72601e04a54c474d9e57b6b0c2d10e9f89aa1a1d9a58dc469a396d31a3f5
|
|
BLAKE2b-256 checksum How to use checksums |
c6c62181604d70b5d0613f4f12f4d8d9ea62c3c68433cf7567e034d4da0c9548
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 19, 2026.
Transparency logSecurity for ionq-core 0.2.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for ionq_core-0.2.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 19, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.