Get Device Details
Get one backend with its basis gates and qubit connectivity.
Use this tool when a workflow needs the hardware constraints of a specific
backend rather than the whole catalog: which gates it supports and which
qubit pairs are physically coupled. Those constraints determine what
transpile_circuits can target.
When to Use:
- Call this after
list_qpus_and_simulatorshas narrowed the choice to onedevice_id. - Call this before transpiling or before explaining why a circuit needs routing on a given backend.
Constraints:
operation_namesandcoupling_maparenullfor backends that publish no transpilation target, which is common for simulators.statusandpending_jobsare point-in-time snapshots.
Notes:
coupling_mapcan hold hundreds of qubit pairs on large QPUs. Checkcoupling_map_edgesfirst and summarize connectivity instead of pasting the full list into agent-facing output.
Args:
device_id: Backend identifier returned by list_qpus_and_simulators.
user: Authenticated user resolved from the API key.
db: Active database session.
Returns: The backend record extended with basis gates and coupling map.
Raises:
HTTPException: Raised with 404 when no backend matches device_id.
Authorizations
Path Parameters
Response
Successful Response
Extend the device catalog entry with transpilation-relevant topology.
Attributes:
last_updated: Timestamp of the last catalog refresh for this backend.
operation_names: Basis gates and instructions the backend supports.
coupling_map: Directed qubit pairs supporting two-qubit operations.
coupling_map_edges: Number of entries in coupling_map, provided so
callers can judge topology size before expanding the full list.