We will be disabling support for TLS 1.0 on June 27, 2018. This may impact third-party integrations using the Captive Portal API, Scanning API, or Dashboard API with these versions of TLS. The third-party service must be updated to use a modern version of TLS.
We will not be able to revert these changes due to the pending PCI deadline on June 30, 2018, so if you notice issues with Meraki services or applications failing due to TLS errors, please contact Meraki support immediately.
Re: Call to Action: Support for TLS 1.0 and 1.1 discontinued
100% support this. There should be no framework that does not support TLS1.2 now.
Could I encourage you to go a step further. api.meraki.com is using a certificate created with a 2048 bit key. I see no reason not to be using 4096 bit keys these days. I use them as standard, and have not run into any compatibility issues on anything.
Also, is there any reason to still offer RSA without ECDHE? For example, you could stop offering these [weaker] ciphers: