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 MultiTxt API.
Important Update: HTTP Endpoints Disabling Soon
From 30 September 2026, we will disable all HTTP endpoints. To ensure uninterrupted service, all integrations must be updated to use secure connections (HTTPS) before this date.
What You Need to Do
- Locate the current API endpoint and look for any URL that starts with:
- http://
- Update the endpoint to HTTPS
- Change the URL so that it starts with https://
Use Secure Connections (HTTPS)
We strongly require that all API requests are made over HTTPS to ensure data is encrypted in transit. As industry standards continue to evolve, secure-only communication is becoming the baseline expectation across platforms.
Adopt Modern TLS Versions
MultiTxt 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
- Update all API requests to HTTPS by 30 September 2026
- 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.