HTTP API Settings
HTTP API Documentation Our complete version 2 API Documentation is here.
The information about your API Keys and SMTP Credentials can be found under two tabs of your Settings screen:
Your API Key is a 96-character single 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 will require this key. It is unique for API connections and separate from SMTP Relay communication.
Manage API Keys
Note: Each account can store up to 10 unique API Keys
Create API Key
New accounts don't have any API Keys on their accounts. Just click this button and create a new key.
At this point you can set custom permissions for this API Key and set optional access restriction for it. The restriction forces the API Key to work only with an IP or IP range that will be specified in this field.
After clicking the Create button, a popup will appear with your newly created API Key. Copy it and save in a safe place. Once you close this window you will not be able to retrieve it. After this step our system will obfuscate it except for the last 5 digits for your security reasons.
Add additional API Key
This option allows you to add more API Keys. This can be useful if you want to share it with someone, but for example, need to set different permissions for it's use. The steps are the same as with the Create API Key part.
This will allow you to change the details of your API Key like permissions or name.
Change API Key
This will generate a new API Key for the particular credentials you chose. This way only the API Key will be changed and the permissions you chose for it will stay the same. This is the only way to regain access to this particular credential if you somehow misplaced the key.
Note: Each account can store up to 10 unique SMTP Credentials
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.
Manage SMTP Credentials
Create SMTP Credential
New accounts do not have any SMTP Credentials. Click this button to create a new one.
Your Elastic Email Account SMTP Username defaults to your Elastic Email Account email address that you use to log in. You can use another email address, but it has to be unique across the entire system - just as with account email addresses. Here you can also set IP access restriction.
After clicking the Create button, a pop up will appear with your newly created SMTP Credential details.
A unique password for your SMTP connection. Copy it and save it in a safe place. Once you close this window you will not be able to retrieve it. After this step, our system will obfuscate it except for the last 5 digits for your security reasons.
Server You can either use smtp.elasticemail.com or smtp25.elasticemail.com
Port 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
Just as with the API Key, you can also Edit, Change or Add other SMTP Credentials.
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.