Instructions and screenshots below may not exactly match the ElasticEmail configuration path you should follow, since ElasticEmail may change them without notice. The ElasticEmail support service can help you to complete the two most impostant steps: validate your domain and get an API key.
Validating your domain
Enter the ElasticEmail console and select “Settings” and then “Domains”. Click on “Add domain”.
Write the domain name you want to verify (without the www).
It will be listed in your configured domain. Now it’s time to change your DNS to add and SPF and a DKIM entry to validate the domain. As your provider for support if you don’t know how to add those entries.
To get the values to be added in your DNS, click the “?” near SPF and near DKIM.
Once the records have been added in your DNS, click “verify” so ElesticEmail will check them. If everything is fine you should get a green check. You may choose to verify only the SPF record, ElasticEmail accepts even only that configuration to validate the domain (but they can change in the future their policy).
Getting an API key
Enter the “Settings” menu and select “SMTP/API”. Your API key is already there, just copy it on this extension configuration:
Do few tests and on success you can enable the extension.
ElasticEmail give you a single API key. If you need more to use them in different services, you can create one or more subaccounts directly from your ElasticEmail console and get a new API key for each account.
For example if you have two blogs and the newsletters are manage by different people, you should create two api key to have more control over the ElastcEmail usage and account reputation.
Subaccount are usually provided to agencies which “resell” the sending service to their customers being able to give them indipendent API key.