Q Ctrl · Authentication Profile

Q Ctrl Authentication

Authentication

Q Ctrl secures its APIs with apiKey across 1 declared security scheme, as derived from its OpenAPI definitions.

CompanyQuantum ComputingQuantum ControlQuantum SensingError SuppressionDeveloper ToolsSDKGraphQL API
Methods: apiKey Schemes: 1 OAuth flows: API key in: account-issued token

Security Schemes

qctrl-api-key apiKey

Source

Authentication Profile

q-ctrl-authentication.yml Raw ↑ 
generated: '2026-07-20'
method: searched
source: https://docs.q-ctrl.com/boulder-opal/get-started
note: >-
  Q-CTRL does not publish a public OpenAPI/Swagger spec. The cloud is reached
  through the official Python clients (boulder-opal, fire-opal), which
  authenticate the caller against the Q-CTRL account service and then call the
  hosted GraphQL API at https://api.q-ctrl.com/graphql.
summary:
  types: [apiKey]
  api_key_in: [account-issued token]
  oauth2_flows: []
schemes:
- name: qctrl-api-key
  type: apiKey
  description: >-
    An account-issued API key (managed at https://accounts.q-ctrl.com) is used
    by the Q-CTRL Python clients to authenticate. Once authenticated, requests
    are made to the Q-CTRL cloud GraphQL endpoint.
  managed_at: https://accounts.q-ctrl.com/
  sources: [docs.q-ctrl.com]
endpoints:
  graphql: https://api.q-ctrl.com/graphql