Get Started - Mailtrap Email API/SMTP (Transactional Stream)

Use Mailtrap Email API or SMTP Service to send emails to recipients’ inboxes on production.

Transactional Stream is separate from Bulk, giving you more options to enhance your deliverability. 

Note: Transactional emails are typically non-promotional emails triggered after the user completes a specific action, for example, welcome emails, password resets, confirmation emails, etc.

Mailtrap Email API/SMTP Overview

Good to know

  • To send emails to your recipients, you must own a domain and add it to Mailtrap. You can, however, use a demo domain to send emails to the email address of the account owner and try out the features of the platform. 
  • Every new domain requires a Compliance Check after DNS verification. If asked, please provide additional details to complete the Compliance Check process. 
  • Mailtrap has Production SMTP for Email API/SMTP and Fake SMTP for Email Testing. They have different hosts and credentials. Please check this setup tutorial if you want to set up a Fake SMTP server.

Start sending Transactional Emails with Mailtrap

Step 1. Try out all the Mailtrap Email API/SMTP features with the demo domain  

You can get started immediately if you use a demo domain. The demo domain is already verified, so that you can explore the platform and try out all of its features. Remember that you can’t send emails to your recipients with a demo domain. 

If you want to, skip the demo domain and go to Step 2 directly. 

Step 2: Verify the sending domain you own 

To add a domain you own, go to the Sending Domains tab and click Add Domain. Type your domain name and confirm with the Add button. 

Then, add the DNS records Mailtrap provides to your domain provider. 

Check our Sending Domain Setup Guide for detailed instructions on adding and verifying your domain. 

Step 3. Integrate your application with Mailtrap SMTP Service/Email API 

To send emails via Mailtrap SMTP, follow the instructions in this article

To send emails via Mailtrap Email API, follow the steps in this article

Why is it critical to use different streams for Transactional and Bulk Email?

The main goal of using different streams is to keep your deliverability high

Mailtrap gives you exactly that - separate Transactional and Bulk Streams. Their infrastructure, IP addresses, and other details are separate. In terms of integration, the streams have different Hosts. 

Though, you don’t need to jump through hoops to set it all up. It’s only a matter of choosing the Transactional Stream and integrating it with your system.

Now, it pays to take a closer look at the benefits. 

  1. Deliverability

By separating your bulk emails from your transactional, mailbox providers (like Google or Yahoo) get a clearer understanding of your sending practices, leading to improved deliverability for each stream.

  1. Straightforward email management 

Separating these two types of emails makes it easier to optimize them and follow the best practices suited for each type. 

Mailtrap allows you to do it with a click; just choose the correct stream, and you’ll get a detailed helicopter view of all the critical Stats, Email Logs, and Suppressions. 

  1. Build greater trust and loyalty

Transactional emails often contain sensitive customer data and need to be delivered promptly and correctly. If these emails do not reach the customer in time or land in the spam folder, it can lead to a loss of trust in your brand.

What else you can do with Mailtrap Email API/SMTP

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Still need help? Contact Us Contact Us