Settings: SMTP / API


Your Elastic Email SMTP & API Settings.

HTTP API Settings

HTTP API Documentation
Our complete version 2 API Documentation is here.

Your API Key is a GUID and it is the key to your account when trying to gain access or make API calls while outside of the User Interface. Every API call and SMTP Relay connection will require this key. It is also your accounts SMTP Relay Password.

Public Account ID
Your Public Account ID is publicly used the unique identifier in GUID format. It is used in Web Forms and Custom Branding integrations.

Manage API Keys

Change API Key
This will generate a new API Key for your account. If you have two API Keys you will have the option to select which API Key you wish to replace.

Add Second Key
This will generate a second API Key for your account.

SMTP Configuration

Almost all third party SMTP clients, Servers, CMSs, and Plugins will use these settings to connect and relay mail through your Elastic Email Account. We don't know of any software that supports SMTP connections that do not work with Elastic Email, but there is a list of CMSs and Plugins that are designed to work specifically with Elastic Email.

Your Elastic Email Account SMTP Username is the same as your Elastic Email Account email address that you use to log in. However, you can also use your Elastic Email API Key as the Username. If you are using cram-md5 authentication you must supply the Email Address for the Username and your Elastic Email API Key for the Password.

Your SMTP Password is your API Key.

You can either use or

We support the following connection ports:

25, 2525, 587, 465

We support TLS and SSL connections. Make sure the connection port you are using is open on your own server.

Using Postfix?
If you are configuring postfix as a local relay make sure you include the following three lines in your postfix configuration

smtp_sasl_auth_enable = yes

smtp_sasl_password_maps = static:yourusername:your api key

smtp_sasl_security_options = noanonymous

API and SMTP limits

20 concurrent requests from single IP
Connection time-out = 600 seconds

20 concurrent requests from single IP
Single command timeout is 2 minutes
Multiple emails can be submitted in one session.


If you like this article, share it with friends:
Share on Facebook
0Tweet about this on Twitter
Share on LinkedIn