Immersive Labs · Authentication Profile

Immersive Labs Authentication

Authentication

Immersive Labs secures its APIs with apiKey and bearer across 2 declared security schemes, as derived from its OpenAPI definitions.

CompanyCybersecuritySecurity TrainingCyber ResilienceWorkforce DevelopmentGraphQLSecurityCompliance
Methods: apiKey, bearer Schemes: 2 OAuth flows: API key in: body

Security Schemes

TokenExchange apiKey
BearerToken http
scheme: bearer

Source

Authentication Profile

immersive-labs-authentication.yml Raw ↑
generated: '2026-07-19'
method: searched
source: https://support.immersivelabs.com/hc/en-us/articles/29622787761809-API-Guide
docs: https://support.immersivelabs.com/hc/en-us/articles/29622787761809-API-Guide
summary:
  types: [apiKey, bearer]
  api_key_in: [body]
  model: >-
    API access key + secret token exchanged for a short-lived bearer access token.
    No published OpenAPI securitySchemes (the API is GraphQL); this profile is
    captured from the provider's API Guide.
schemes:
- name: TokenExchange
  type: apiKey
  description: >-
    An API key generated in the platform (Settings) yields an Access key and a
    Secret token. These are POSTed as form fields username={access_key} and
    password={secret_token} to the public tokens endpoint to obtain an access token.
  token_endpoint: https://api.immersivelabs.online/v1/public/tokens
  request: >-
    curl -X POST -d 'username={access_key}&password={secret_token}'
    https://api.immersivelabs.online/v1/public/tokens
- name: BearerToken
  type: http
  scheme: bearer
  description: >-
    The access token returned by the tokens endpoint (UUID format) is sent as an
    Authorization: Bearer {token} header on subsequent GraphQL requests. Tokens
    expire 30 minutes after issue and must be re-minted.
  token_ttl_seconds: 1800
notes:
- Both the REST and GraphQL surfaces require API-key authentication.
- The V1 GraphQL API is no longer actively enhanced; API V2 is the active surface.