When Mandrill announced they were doing away with their free tier, many of you looked for new options and we’re proud that we were able to provide a solution for so many members of our community. Through your feedback, we heard that you wanted subaccounts and we’re thrilled to announce that they are now available!
The new subaccounts feature will allow you to support separate business units, mail streams, or customers (if you are an email service provider or consultant) all from within your SparkPost account. Subaccounts enable you to give each of these units direct access to the SparkPost messaging service APIs. (Subaccount users will not have separate access in the UI.) Also note, Heroku users will not be able to use subaccounts.
Subaccounts can be used in a variety of ways depending on your needs. The most common reason to set up subaccounts is to separate assets (such as sending domains and API keys) so that each unit can access/use SparkPost and to separate reporting data. Some common use cases for subaccounts are:
- You are a service provider for multiple unique customers.
- You have unique internal business units who operate independently from one another.
- You have a particular mailstream/campaign that is mission critical and you wish to track and sequester its data separately from other mailstreams/campaigns.
As a Master account owner you only need to give your customer/subaccount user(s) the subaccount API key – they will use it for all operations afforded via the default API key created upon subaccount creation.
For more information on creating, reporting and status details, please check out the subaccount support article.
For future subaccount features, you can check back on the support article for updates or the blog.