Kaleyra offers email API service, a channel through which customers can send emails to a specific recipient or to multiple recipients at once, along with attachments.
In order to enable email channel for your account, contact your Kaleyra Account Manager or the support team, see: support. Share the domain name (from email addresses) from which the Email has to be sent. The domain is then whitelisted by the Kaleyra team and the Email service is enabled from then on.
The different services that email API offers are:
- Send single email
- Send bulk email
- Send batch email
- Send attachments with email
- Create email templates to send emails
- Use webhook to get notified about successful email delivery or email bounce.
Email Service Pricing
The email channel service is specified at the background software and a service price charged for every email successfully delivered. These settings are made by the account manager. Based on the number of emails delivered, the corresponding amount is deducted from the budget available at the account level. The service pricing applies to all the single, batch, and bulk emails.
Suppose, the cost of sending an email is $1 and the budget available at the account level is $200. If there are 10 emails sent in a batch, then $190 budget amount remains at the account level after deducting $10 for the email service.
Note: You can know how much budget is is used up for sending a single, batch, or bulk emails using the 'get logs' API.
Kaleyra Email API supports the latest security protocols to ensure that the Emails reach untampered to the recipients' inbox.
The three main protocols implemented for email security are:
- Sender Policy Framework (SFP)
- Domain Keys Identified Mails (DKIM)
- Domain-based Message Authentication, Reporting, and Conformance (DMARC).
Using the SFP authentication standard, the IP addresses that are authorized to send emails for a particular domain are defined. When an email is received, the actual IP address of the email is compared with the list of IP addresses saved for the domain. This security measure prevents fraudulent use of the domain name through phishing attacks.
Using the DKIM protocol, a public key is issued to the customer by Kaleyra for the domain name. The customer can send emails using the customer's domain name to the end-users. This security model enables the end-users to identify that the email is from an authenticated customer and is not tampered during the transmission by any third party.
The DMARC protocol unifies the SFP and the DKIM protocol authentication process and allows the domain owners to define how they want to handle an email that fails the security checks. With its 'policy(p) tag', DMARC allows domain owners to define what should happen, if either or both SPF and DKIM checks fail.
The 'policy(p) tag' allows the following three values when the security checks fail:
'none'—no action is taken when the security checks fail.
'quarantine'—the message is quarantined and sent to spam folder
'reject'—the message is rejected and deleted.
Updated 5 days ago