University of Calgary · Authentication Profile

University Of Calgary Authentication

Authentication

University of Calgary secures its APIs with apiKey and http across 3 declared security schemes, as derived from its OpenAPI definitions.

EducationHigher EducationUniversityResearchOpen DataRepositorySpace PhysicsCanada
Methods: apiKey, http Schemes: 3 OAuth flows: API key in: header

Security Schemes

AccessToken http
scheme: bearer
ApiKeyAuth apiKey
· in: header (x-aurorax-api-key)
APIKeyHeader apiKey
· in: header (x-srs-api-key)

Source

Authentication Profile

Raw ↑ 
generated: '2026-07-11'
method: derived
source: openapi/university-of-calgary-aurorax-api.yaml, openapi/university-of-calgary-srs-api.yaml
summary:
  types:
  - apiKey
  - http
  api_key_in:
  - header
schemes:
- name: AccessToken
  type: http
  scheme: bearer
  bearerFormat: Generated by server
  description: Send the Authorization header found in the response of a successful /authentication
    request on all  secure endpoints. Copy it verbatim to the request header. It is fine to
    send this header on all requests  to the API. The value in Swagger UI should only include
    the access token part (leave out 'Bearer').
  sources:
  - openapi/university-of-calgary-aurorax-api.yaml
  - openapi/university-of-calgary-srs-api.yaml
- name: ApiKeyAuth
  type: apiKey
  in: header
  parameter: x-aurorax-api-key
  description: API keys are intended to be used by non-interactive software interfacing with
    the REST API. These can  be used instead of an Access Token approach.
  sources:
  - openapi/university-of-calgary-aurorax-api.yaml
- name: APIKeyHeader
  type: apiKey
  in: header
  parameter: x-srs-api-key
  sources:
  - openapi/university-of-calgary-srs-api.yaml