At Sinch, we’re committed to helping you maintain secure and reliable integrations. As part of this effort, we’d like to share a few recommended best practices for using the Sinch Engage API.
Use Secure Connections (HTTPS)
We strongly recommend that all API requests are made over HTTPS to ensure data is encrypted in transit. If any of your integrations currently use HTTP, we advise updating them to HTTPS to align with modern security standards. As industry standards continue to evolve, secure-only communication is becoming the baseline expectation across platforms.
Adopt Modern TLS Versions
Sinch Engage supports TLS 1.2 and TLS 1.3. Earlier versions (TLS 1.0 and 1.1) are no longer supported. For improved security and performance, we recommend using TLS 1.3 wherever possible. Modern TLS versions are increasingly expected to meet security and compliance requirements.
Summary of Recommendations
Use HTTPS for all API requests
Ensure your systems support TLS 1.2 or higher
Prefer TLS 1.3 for optimal security and efficiency
Following these practices will help ensure your integration remains secure, performant, and aligned with industry standards as they continue to evolve.