For most of our end-users, and developers accessing our API, this change will be transparent and nothing is required on your part. Your web browsers already support wildcard certificates, as do our iOS and Android device clients.
While the CA chain remains the same for the new certificate, some developers or users of our API may be using older SSL libraries that do not support wildcard certificates when doing SSL hostname verification. This may cause SSL validation errors and prevent your scripts and applications from properly accessing our API. Most modern SSL libraries like OpenSSL, as well as any clients that use it like curl, do support wildcard certificates.
In order to test your applications with our new certificate, we have setup https://newapi.pushover.net/ with the new wildcard certificate. All existing API endpoints are the same at the new host:
Note: This new hostname is for short-term testing only, and should not be used in your production environment. On March 1, 2014, we will switch to the new wildcard SSL certificate everywhere and the newapi.pushover.net DNS record will be removed.
If you have any questions about this change, please feel free to contact us.