Symptom
I am getting a TLS error when trying to submit an HTTPS request to api.nexmo.com or rest.nexmo.com.
Applies To
- TLS Certificates
- HTTPS Request
- Error Message
Resolution
Our endpoints use TLS certificates, signed by public certificate authorities, to ensure the security of our communications with our customers and partners. If you have any issue initiating encryption with our endpoints, or face any certificate-related rejection, you may need to update your chain of trust.
- Retrieve the root and intermediate certificate bundle from here: https://cacerts.digicert.com/DigiCertTLSRSASHA2562020CA1-1.crt.pem
- Export them to the format you prefer.
- Import them into your application(s).
- Optionally, if you need to directly import our certificates as well, you can find them here:
- For HTTPS or any other non-SMPP endpoint: https://static.nexmo.com/tls/2022-06/wildcard.nexmo.com.pem
Additional Information
We strongly recommend to all of our users that they not directly store certificates in their environments, as they may be subject to change without prior notice. Instead, we encourage you to use the standard best practices and trust the public Certificate Authority (DigiCert), which has signed our certificates.
Articles in this section
- How fast can I send Redact API requests?
- How fast can I send Numbers API requests?
- What are Vonage's HTTP session time-out limits for a webhook response?
- What time zone are Vonage API logs in?
- TLS Error Submitting HTTPS Request to Vonage API
- Special Characters Not Displaying When Sent
- Can I use a static IP address instead of rest.nexmo.com or api.nexmo.com?
- Can I append custom parameters to the Webhook URL?
- How to Build a REST Implementation that Scales Better Than SMPP
- How quickly can I connect to Vonage using the REST API?