To operate correctly, Krisp needs to periodically communicate with our backend servers. That is done through certain domains. Specific events can be triggers for connection. For each domain, there is an expected payload.
Read more about whitelisting and firewall/proxy configuration in this article.
The table below will give you an overview of the domains, how often Krisp communicates with the servers through them, in which cases, and what the expected payload is.
| Domain: krisp.ai |
Connection event Accessing the main website and logging into the account Frequency of connection No pre-set frequency. Triggered by user action Expected payload No substantial payload |
| Domain: api.krisp.ai |
Connection event - Connection to Krisp servers and syncing configuration - Login to the account, logout, profile sync, free minutes balance sync (free users), app update check Frequency of connection - Every time at application startup - Sync every 6 hours - Can also be triggered by user action Expected payload 0-1KB payload in request/response |
| Domain: account.krisp.ai |
Connection event - Connection to Krisp servers and syncing configuration - Login to the account, accessing the account Frequency of connection No pre-set frequency. Triggered by user action Expected payload No substantial payload |
| Domain: help.krisp.ai |
Connection event - Accessing the Krisp help center - Contacting Krisp support Frequency of connection No pre-set frequency. Triggered by user action Expected payload No substantial payload |
| Domain: cdn.krisp.ai |
Connection event - Showing the onboarding videos, - Downloading app installers for first-time installation and updates, etc. Frequency of connection No pre-set frequency. Triggered by user action Expected payload - Installer package ~130 MB - Videos 15-60 MB |
| Domain: analytics.krisp.ai |
Connection event Sending the collected analytics data. Frequency of connection - Every time at application startup - Sync every 1 hour Expected payload Depending on the amount of analytics data being sent to the servers, can result in 1-100KB payload in request/response |
| Domain: upload.krisp.ai |
Connection event Sending problem reports from the Krisp app Frequency of connection No pre-set frequency. Triggered by user action Expected payload Depending on the contents of the report, can result in 100KB - 8MB payload |
| Domain: sentry.io |
Connection event Sending app crash reports Frequency of connection No pre-set frequency. Triggered by occurrence Expected payload ~100KB payload |
| Domain: metabase.krisp.ai |
Connection event Used for analytics dashboard Frequency of connection No pre-set frequency. Triggered by user actions Expected payload The payload is not fixed; each dashboard has a different payload |
| Domain: wss://websocket.krisp.ai |
Connection event Used for keeping active connection, updating user profile data, uploading Frequency of connection There is no pre-set frequency; the connection is triggered by admin or user actions Expected payload The payload is not fixed; each event has a different payload |