Integrated API Client Docs, Dedicated IP Pooling, and Better Session Timeouts

We've got a lot of projects currently in the Research & Development phase, but we've still got some cool new features to announce this week. We've overhauled our API docs to support multiple programming languages, added flexible traffic splitting for dedicated IPs, and improved session handling.

Integrated API Client Documentation

Reading API docs when trying to integrate a service into your application can be a confusing process. Part of this is because the actual interface you're using as a programmer usually isn't the raw protocol. It's a library that is generally similar to the API but just different enough to be annoying. This can lead to mental contortions trying to map between what's in the API docs and how the library implements the call. We're trying to reduce that confusion by integrating our official API client libraries into our API docs.

You can now choose one of three different programming languages (plus curl) and see every call and all the documentation contextualized for the client library. This is all driven by the same scripts we use to generate our API documentation and the API clients themselves, so these docs will be always be in sync and updated automatically as the API changes. In the coming weeks, we'll be adding even more languages, so stay tuned.

Dedicated IP Pooling

As your mail volume grows, it can be helpful to use different IPs for different types of mail. ISPs only accept mail so quickly, and if you're sending large enough amounts of email, you'll eventually run into those limits. For bulk email, that's not a big deal, and we already support adding multiple IP addresses to ensure that your mail will always be delivered quickly. But if, like many of our users, you send a mixture of bulk and transactional email, you might want to avoid having your time-sensitive transactional messages sit in the queues behind a newsletter.

We've added the ability to define multiple pools of dedicated IPs within a single Mandrill account. When you send mail, either via the API or SMTP, you can indicate which pool to use, and our routing engine will take it from there.

Password Confirmation for Dangerous Pages

Session timeouts are a tricky and dangerous thing. Having sessions last forever is more convenient for users, but can reduce the security of the account if the computer is shared. We're cautious as a general rule over here, so we had sessions time out after 20 minutes of inactivity. But, we got tired of getting kicked out of the app all the time, so now we're ready to take a more nuanced approach.

The general session timeout for all Mandrill accounts has been raised to 10 hours. However, if you attempt to access a page that we consider sensitive, we'll ask you to confirm your password before allowing you access. This password confirmation will expire after 30 minutes. If you have Mandrill in a background tab that you switch to now and again to see the stats, your session should last a full business day without needing to log in again.