In version 2.0 of MailChimp’s API, there was a helper/ping endpoint, which is useful for automated monitoring (e.g. Nagios checks.)
This no longer exists in v3.0, which is quite a bit different.
Just to share the recommendation their API support team gave me, use the API Root resource instead, and assuming you don’t need all the data it returns, just append
?fields=account_name and it will only send that specific field back.
I’d recommend logging the HTTP response code too and checking it’s 200, e.g. in PHP:
$http_status = curl_getinfo( $ch, CURLINFO_HTTP_CODE );
MailChimp have just announced that Mandrill, their transaction email service, is being discontinued as a standalone product over the next couple of months. In future all accounts will need to be tied to a MailChimp paid plan.
There are various options should you decide to take the opportunity to migrate elsewhere (MailChimp themselves mention Amazon SES) but I’d like to put in a good word for Postmarkapp; they’ve been around for ages (the company is Wildbit who also make Beanstalk), the site is nicely presented but simple and easy to use, they’re very open about how they work and they’ve launched an excellent Templates featured which I tried a few months ago.
Update 27 Feb:
Here’s a StackOverflow answer by me for anyone who sees this error:
…when using the MailChimp API.
The problem is due to MC using a root certificate that’s been removed from the Mozilla certificate bundle (you’re most likely to see it on Debian systems.)
This is a safer way to work around the problem that rolling all your certificates back to 2014 or disabling SSL certificate verification entirely. You also won’t need to set cURL options or edit your php.ini.
Also covered: how to ‘ping’ the MailChimp API to check it’s working.