SuperOps · Authentication Profile
Superops Authentication
Authentication
SuperOps GraphQL APIs authenticate with a personal API token passed as an HTTP Bearer token, combined with a mandatory CustomerSubDomain header that identifies the tenant. There is no OAuth 2.0 / OpenID Connect flow; the token is generated in the SuperOps app and a tenant may hold only one active token at a time.
SuperOps secures its APIs with http-bearer and apiKey across 2 declared security schemes, as derived from its OpenAPI definitions.
CompanyIt Management SoftwarePSARMMMSPService DeskEndpoint ManagementIT DocumentationGraphQL
Methods: http-bearer, apiKey
Schemes: 2
OAuth flows:
API key in: header
Security Schemes
BearerToken http
CustomerSubDomain apiKey