Krisp domains, connection events, and expected payloads

To operate correctly, Krisp periodically communicates with our backend servers through a set of domains. Each connection is triggered by a specific event and carries an expected payload.

Info

Read more about allow-listing and firewall/proxy configuration for your Call Center AI team in this article.

The table below gives you an overview of the domains, how often Krisp communicates with the servers through each one, in which cases, and what the expected payload is.

Domain	Connection event	Frequency of connection	Expected payload
krisp.ai	Accessing the main website and logging into the account	No preset frequency; triggered by user action	No substantial payload
api.krisp.ai	Connecting to Krisp servers and syncing configuration Logging in, logging out, profile sync, and app update check	At every application startup Sync every 6 hours Can also be triggered by user action	0-1 KB payload in request/response
account.krisp.ai	Connecting to Krisp servers and syncing configuration Logging in and accessing the account	No preset frequency; triggered by user action	No substantial payload
help.krisp.ai	Accessing the Krisp Help Center	No preset frequency; triggered by user action	No substantial payload
krispai.zendesk.com	Contacting Krisp Customer Engineering	No preset frequency; triggered by user action	Not fixed; each submission has a different payload depending on the log file size
cdn.krisp.ai	Showing the onboarding videos Downloading app installers for first-time installation and updates	No preset frequency; triggered by user action	Installer package ~130 MB Videos 15-60 MB
analytics.krisp.ai	Sending the collected analytics data	At every application startup Sync every hour	1-100 KB payload in request/response, depending on the amount of analytics data being sent
upload.krisp.ai	Sending problem reports from the Krisp app	No preset frequency; triggered by user action	100 KB to 8 MB payload, depending on the contents of the report
sentry.io	Sending app crash reports	No preset frequency; triggered by occurrence	~100 KB payload
metabase.krisp.ai	Used for the analytics dashboard	No preset frequency; triggered by user actions	Not fixed; each dashboard has a different payload
wss://websocket.krisp.ai	Keeping the connection active, updating user profile data, and uploading	No preset frequency; triggered by Admin or user actions	Not fixed; each event has a different payload

Related articles