Domain Allowlist
Considering the increasing level of cyber threats and security risks for public-facing applications, Kaleyra CPaaS has introduced support for strict Cross-Origin Resource Sharing (CORS) validation and management for any browser-based calls to the Kaleyra application from domains other than kaleyra.io itself.
CORS is a browser security mechanism that controls whether a web application running on one domain is allowed to access resources hosted on another domain.
For example, if your web application is hosted on https://www.mycompany.com and needs to communicate with the Kaleyra CPaaS APIs hosted on a different domain, the browser may block these requests unless the CPaaS platform explicitly allows them.
To enable this communication, the CPaaS platform must be configured to allow requests from the relevant domains (origins).
By default, Kaleyra CPaaS applies a strict “Same Origin” policy, meaning that only web-browser based calls coming from the Kaleyra origin (that is, through Kaleyra CPaaS UI) are allowed.
Domain Allowlist functionality allows you to configure any additional domains from which your web-browser may call the Kaleyra CPaaS API.
Notes:
- CORS restrictions are enforced by web browsers. They do not apply to API requests made directly from backend servers or server-to-server integrations.
- If you are using only Kaleyra CPaaS UI or have only server-to-server API integration, no configuration is required in the Domain Allowlist.
- Domain Allowlist configuration is required if you invoke the Kaleyra CPaaS API from a different web-based platform directly from the browser (for example, your CRM or Campaign Management platform).
- Any calls to the Kaleyra API coming from a domain that is not “Same Origin” as the Kaleyra CPaaS application and that is not configured in the Domain Allowlist will be blocked.
The Domain Allowlist feature allows you to add an account-level domain allow-list to improve API security while maintaining compatibility with existing browser-based integrations.
In the case of Sub accounts, by default, all the configured domain allowlists are inherited by the Sub account.
Benefits of Domain Allowlist
The following are the benefits of the domain allowlist:
Improved API Security for web-browser based call
Only approved and trusted domains can access the APIs from a web-browser call. It helps reduce the risk of unauthorized access.
Protection Against Cross-Origin Attacks
Prevents malicious websites from making illicit API requests.
Better Access Control
You can explicitly manage which domains are allowed to interact with APIs from a web browser.
Reduced Risk of Misuse
Limits API exposure to known Origins, helping prevent abuse and exploitation.
Support for Browser-Based and CTI Integrations
Secures integrations while allowing legitimate browser and CTI use cases.
Account-Level Flexibility
The domain allowlist can be updated as business requirements or domains change.
Backward Compatibility
Existing integrations continue to work, minimizing disruption during adoption.
Enhanced Compliance and Governance
The domain allowlist provides stronger control and auditability over API access policies.
Limitations:
- A maximum of five domains can be configured.
- Domain name cannot exceed 253 characters.
- A duplicated domain is not allowed.
The sections contain the following topics:
Updated about 14 hours ago

