Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.quarterzip.ai/llms.txt

Use this file to discover all available pages before exploring further.

​
Device requirements

Quarterzip makes use of the getDisplayMedia() web API which typically isn’t available on mobile devices. This can be guarded against using the following logic: 
const canUseQuarterzip = !!(navigator.mediaDevices?.getDisplayMedia);

​
Required CSP Directives

If your application makes use of the Content-Security-Policy header or the equivalent <meta> tag, please ensure the following directives are set.

​
Directive: connect-src

The SDK makes runtime connections to the following origins:
OriginPurpose
https://*.quarterzip.aiQuarterzip API requests
https://*.daily.co
wss://*.daily.co		The transport layer that facilitates call connectivity.
https://firestore.googleapis.comDatabase operations
https://*.firebaseio.com
wss://*.firebaseio.com		Realtime listeners
https://securetoken.googleapis.com
https://identitytoolkit.googleapis.com		User auth
https://storage.googleapis.comCDN

​
Directive: script-src

OriginReason
https://*.quarterzip.aiQuarterzip SDK JS
https://*.daily.coRequired by the Daily transport layer

​
Required Permissions-Policy

In addition to CSP, if your website defines the Permissions-Policy header (or equivalent <iframe allow> attribute), the following directives must be set:
  • microphone — Required for audio capture during calls
  • display-capture — Required for screen sharing
  • speaker-selection - Required for selecting audio outputs

​
SPA routing

The SDK maintains an active WebRTC connection for call state and audio streaming, tied to the lifecycle of the current page. A full page reload, whether from the user refreshing the browser, calling window.location.reload(), or navigating in a multi-page app, will immediately drop the call. There is no automatic reconnection; the user must rejoin. For this reason, the SDK should only be used within a single-page application (SPA) where navigation is handled client-side.