We are now sending the emails via API
SMTP is Dead.
SMTP vs. API? I just want to send my email! If this is what you’re thinking – fear not! While there is a lot of complicated-sounding terminology when sending email, you don’t need to understand all the ins and outs to make the right choice.
When you use NIZU as your transactional ERP email provider, you have 4 choices for connecting your email or app to the NIZU email service: SMTP, Google OAuth2, Microsoft OAuth2, and API.
Both options have their pros and cons. In this post, I’ll explain the differences between these two methods so you can choose the right choice for your email needs.
NIZU offers 4 options for sending a transactional email: over SMTP or with the ElasticMail, Mailgun, and SendGrid API.
SMTP is the traditional method for sending email. It has been the standard for email sending over the Internet since the 1980s. It involves setting up an email server and relaying messages.
On the other hand, an API for email sends emails directly from an application to an email service provider, bypassing the need for a separate email server.
Sometimes, you won’t have the opportunity to choose which option you use to send emails. For example, many websites allow you to set custom SMTP settings for sending emails but have no option for sending through an API.
But if you’re building an app or can choose between SMTP vs. API for sending email via a plugin or website, you should understand the differences between SMTP and API.
The choice between SMTP and API can affect email deliverability, speed, scalability, and the ability to track and analyze email performance.
You can still use NIZU Cloud API to send your invoices. Check our API Documentation here
The email reading confirmation will remain a feature of NIZU only if your provider does not replace the links or the pixel images