Tip: Full details of TLS versions and cipher suites currently supported by the Twilio REST API are available from SSL Labs.Ĭertificate Chain: To establish a secure connection, HTTP clients must verify our certificate chain and root authority. Requirement: HTTP clients must negotiate a supported TLS version and cipher suite. For more details, please see Twilio REST API’s TLS and Cipher Suite Security Changes for June 2019. Support for earlier versions was removed in June 2019. TLS Versions and Cipher Suites: Twilio’s REST API currently supports only TLS v1.2. Tip: Be sure your DNS cache respects Twilio’s TTL of 60 seconds to avoid making requests to stale IP addresses. Requirement: Firewalls and proxies must allow HTTPS traffic to any public IP address or, or allow Twilio’s subdomains (e.g. IP Addresses: Twilio’s cloud infrastructure dynamically assigns IP addresses for the REST API from a large range of Amazon Web Services (AWS) IP addresses, and those IP addresses can change without advance notice.
Tip: If your machine can browse, your network allows access. Requirement: Firewalls and proxies must allow outbound HTTPS traffic on port 443 to connect to the REST API. HTTPS: All traffic to the REST API uses HTTPS on standard port 443 and is accessible via any HTTP client, including web browsers. Notice: Be sure to check Twilio’s status page for any current issues. T his guide covers helpful information for configuring your environment to connect to the Twilio REST API and troubleshooting common issues. All connections to the Twilio infrastructure have the same connectivity requirements, regardless of the product used or the subdomain being accessed.
0 kommentar(er)
