Nexus API Deprecation
The following table summarizes REST API breaking changes in Nexus. These changes apply only if you are using the REST APIs directly, otherwise Quantinuum recommends all users download and use the latest version of qnexus.
These endpoints will be deprecated on 30 August 2025 and will be removed on 30 November 2025. The first column specifies the HTTP method. ALL means GET, POST, PATCH, PUT, DELETE will be removed. The second and third columns contain old and new API endpoints. There are no breaking changes expected for the web portal user experience or python qnexus API.
| API Call | Deprecated Endpoint | Replacement Endpoint | User Experience Change |
|---|---|---|---|
| ALL | /api/aggregates/v1beta/** | /api/aggregates/v1beta2/** | |
| ALL | /api/assignments/v1beta/** | /api/assignments/v1beta2/** | |
| ALL | /api/v5/backend_info/** | - | |
| ALL | /api/backend_snapshots/v1beta/** | /api/backend_snapshots/v1beta2/** | |
| ALL | /api/circuits/v1beta/** | /api/circuits/v1beta2/** | |
| ALL | /api/compilation_passes/v1beta/** | /api/compilation_passes/v1beta2/** | |
| ALL | /api/compilations/v1beta/** | /api/compilations/v1beta2/** | |
| ALL | /api/v5/experiments/** | - | |
| ALL | /api/v6/jobs/** | /api/jobs/v1beta3/** | Add system name column to jobs list dataframe |
| /api/jobs/v1beta/** | Replace StatusEnum with JobStatusEnum in JobStatus class to ensure correct status handling in job management | ||
| /api/jobs/v1beta2/** | Add retrying and cancelling status to JobStatusEnum | ||
| Add depleted and terminated statuses to JobStatusEnum and related filters | |||
| ALL | /api/licenses/v1beta/inquanto/** | /api/licenses/v1beta2/inquanto/** | |
| GET | /api/v6/orgs/** | /api/orgs/v1beta2/** | |
| POST | /api/v6/orgs/** | /api/orgs/v1beta2/** | |
| GET | /api/v6/orgs/{organisation} | /api/orgs/v1beta2/{organisation} | |
| GET | /api/v6/orgs/{organisation}/users | /api/orgs/v1beta2/{organisation}/users | |
| DELETE | /api/v6/orgs/{organisation}/user-group/{group_id}/quota/{quota_id} | /api/orgs/v1beta2/{organisation}/user-group/{group_id}/quota/{quota_id} | |
| DELETE | /api/v6/orgs/{organisation} | /api/orgs/v1beta2/{organisation} | |
| ALL | /api/projects/v1beta/** | /api/projects/v1beta2/** | |
| ALL | /api/property_definitions/v1beta/** | /api/property_definitions/v1beta2/** | |
| ALL | /api/quotas/v1beta/** | /api/quotas/v1beta2/** | |
| ALL | /api/quotas/v1beta2/** | /api/quotas/v1beta2/** | |
| ALL | /api/results/v1beta/** | /api/results/v1beta3/** | Update results fetching to allow incomplete results for different statuses |
| /api/results/v1beta2/** | |||
| ALL | /api/v6/teams/** | /api/teams/** | |
| ALL | /api/teams/v1beta/** | /api/teams/v1beta2/** | |
| ALL | /api/v5/user/** | /api/users/** | |
| GET | /api/qsysresults/v1beta | /api/qsysresults/v1beta2 |
How can users access a complete specification of REST API Endpoints?
All REST API endpoints are available at this URL (Nexus API Docs). The REST API is consumed by the qnexus Python API. Changes to the REST API may impact qnexus consumption.
Next Steps?
Updating to the latest qnexus version should mean that new APIs are automatically used. We will work to update qnexus to ensure that no/minimal changes to python code are needed. A detailed changelog for qnexus is available here.
Users should inspect the REST API endpoints to ensure their workflows are not impacted. Please contact QCSupport@quantinuum.com for more information if required.