generated: '2026-07-19'
method: searched
source: https://docs.frvr.com/
docs:
  - https://docs.frvr.com/start/overview/
  - https://docs.frvr.com/start/configuration/
  - https://docs.frvr.com/start/environments/
  - https://docs.frvr.com/modules/auth/
summary: >-
  Cross-cutting semantics for the FRVR games SDK. The developer surface is a single
  JavaScript SDK (FRVR.*) that adapts per distribution channel; there is no public
  REST/HTTP API, so conventions are expressed as SDK contracts (namespaces,
  lifecycle hooks, capability gates) rather than headers/pagination.
integration_style:
  surface: JavaScript SDK loaded via two <script> tags (core + channel bundle)
  namespace: single global FRVR object with per-module namespaces (FRVR.ads, FRVR.iap, FRVR.auth, FRVR.tracker, ...)
  config: FRVR.config.* — usually generated by FRVR per studio/release
  bootstrap: FRVR.init(mode) with mode in {dev, beta, prod}
authentication:
  style: JWT bearer via SDK (FRVR.auth.getAccessToken())
  ref: authentication/frvr-authentication.yml
lifecycle:
  required_hooks: >-
    Web integrations must wire five FRVR.lifecycle.* hooks and the bootstrapper
    flow; Unity/Cocos/Construct wrappers handle lifecycle automatically.
  ref: https://docs.frvr.com/engines/web/lifecycle/
capability_gates:
  pattern: >-
    Feature support varies by channel; every module exposes runtime isSupported /
    canX checks (e.g. isInterstitialReady, canScheduleMessages, canCreateShortcut,
    allowsExternalLinks) so games degrade gracefully per platform.
  ref: https://docs.frvr.com/reference/channels/
environments:
  modes: [dev, beta, prod]
  ref: sandbox/frvr-sandbox.yml
storage:
  local: per-device async key-value (FRVR.storage local)
  cloud: server-backed cross-device key-value
analytics:
  tracker: FRVR.tracker.ftue / levelStart / levelEnd / logEvent / logValuedEvent
idempotency:
  supported: false
  note: No idempotency-key contract is documented for the SDK.
pagination:
  supported: false
  note: Leaderboard/tournament queries are range/timeline based, not cursor-paginated per docs.
versioning:
  scheme: bundle-versioned; FRVR's pipeline injects the correct channel bundle per release
error_handling:
  style: per-module callbacks (onStart/onError/onFinish) and promise rejections; no RFC 9457 problem+json envelope (non-HTTP surface)
consent:
  cmp: IAB TCF v2, CookiePro
  ref: conformance/frvr-conformance.yml