EmbodyMe · Authentication Profile

Embodyme Authentication

Authentication

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

CompanyArtificial IntelligenceAvatarsDigital HumansNeural RenderingFace TrackingGenerative AIVideo GenerationReal-TimeStreamingSDK
Methods: apiKey Schemes: 1 OAuth flows: API key in: header

Security Schemes

DigiselfApiKey apiKey
· in: header (x-api-key)

Source

Authentication Profile

embodyme-authentication.yml Raw ↑ 
generated: '2026-07-19'
method: searched
source: https://github.com/embodyme/digiself-realtime-api-sample
docs: https://github.com/embodyme/digiself-realtime-api-sample/tree/main/quick-start-meeting-bot
summary:
  types: [apiKey]
  api_key_in: [header]
  oauth2_flows: []
schemes:
- name: DigiselfApiKey
  type: apiKey
  in: header
  parameter: x-api-key
  description: >-
    All DigiSelf Realtime/Stream API requests are authenticated with a
    per-account API key sent in the x-api-key request header (documented as
    DIGISELF_API_KEY in the sample apps). API access is provisioned on the
    DigiSelf Business plan. Sample backends also carry an OPENAI_API_KEY for the
    OpenAI Realtime API leg, which is a separate third-party credential and not
    part of DigiSelf auth.
  sources:
  - https://github.com/embodyme/digiself-realtime-api-sample
notes:
- No OpenAPI/Swagger securityScheme is published; this profile is captured from
  the official digiself-realtime-api-sample repository documentation.
- No OAuth2/OpenID Connect surface was found; auth is single API key only.