Skip to content

Configuration (Networking)

Goal

This document is the canonical reference for networking-related configuration variables, which are read from the app's Info.plist at runtime (injected via Build Settings).

Canonical Code

  • ecall/Core/Networking/Endpoints.swift (AppEnvironment, reads Info.plist values injected from build settings)
  • ecall/Core/Networking/APIEndpoint.swift (constructs REST and WSS URLs)
  • ecall/Core/Networking/APIClient.swift (uses APP_API_ID / APP_API_HASH)

Variables

Environment

  • ENVIRONMENT_NAME: Dev, Staging, or Production. Determines which set of URLs and keys to use.
  • APP_STORE_ID: App Store app ID, appended to share-contact links as aid.

Infrastructure URLs

  • API_BASE_URL: The base URL for the REST API (e.g., https://api.example.com).
  • SOCKET_BASE_URL: The base URL for the STOMP WebSocket (e.g., wss://api.example.com).
  • KT_URL: The Key Transparency server base URL used by TKSAPIService.
  • LIVEKIT_URL: The full URL for the LiveKit server (e.g., wss://livekit.example.com).

Request Signing

  • APP_API_ID: Used for the X-Api-Id request header.
  • APP_API_HASH: The secret key used to generate the X-Signature HMAC header.
  • GOOGLE_CLIENT_ID: Google Sign-In client ID.
  • SHARE_URL: Base share URL. Contact links are built as {SHARE_URL}/contact/{token}?aid={APP_STORE_ID}.
  • BUNDLE_URL_SCHEME: Custom URL scheme for app deep links.
  • BASE_DOMAIN: Partner domain used by universal-link validation.
  • FAQ_URL: Partner FAQ/support URL.
  • Partner Configuration: For a guide on how partners should set these variables, see ../../partner/partner-technical.md.
  • API Client Behavior: For details on how signing headers are used, see ./api-client.md.
  • SSL Pinning: For details on how these URLs are affected by SSL pinning, see ../security/ssl-pinning.md.