Example HTML page

# What SENDUNE is the go to email platform for anyone using AWS SES. #### **SENDUNE makes it very easy to use AWS SES. It integrates with your AWS account and abstracts away all the complexity of sending transactional and marketing messages**. #### Here's a brief overview of how things work. When a user signs-up on your web or mobile app, you insert their details (name, email, number, etc.) into SENDUNE. Thereafter any action done by that user can be inserted and tracked in SENDUNE. For example if a user adds 'purple pants' to their wish-list, you attach the tag 'purple pants' to that user. All of this is done using the '[Contacts API](/contacts)'. You can then filter your users using a combination of tags to send targeted messages (Emails, SMS, OTP's). Messages can be sent manually, programmatically (API), or by using workflow/automation rules. For example you can trigger a workflow as soon as a particular tag is added to a contact. SENDUNE [integrates](/get-started) with your own AWS account to send messages. Why? Because AWS is unbeatable in terms of cost and message reliability. SENDUNE uses the following services within your AWS account. | AWS Service | Purpose | | -------------------------------------------- | -------------------------------------------------- | | SES | to send emails | | SNS, Cloudwatch | for email statistics (delivery, open, click, etc.) | | S3 | to store images associated with your emails | | SQS (legacy - only for accounts before 2021) | for queuing and processing delivery statistics | # Why [AWS SES](https://aws.amazon.com/ses/) delivers more than a **trillion emails** each year for customers like **Netflix, Reddit, and** **Duolingo**. It has the same reliability and deliverability as any other email service and it comes at a phenomenal price point. Yet you burn time and money on third party email services.\ \ Yes, SES is complex. There's tons of documentation to deal with. SENDUNE eliminates all this complexity. SENDUNE is a fully hosted service and comes with a 99.95% uptime SLA.\ \ SENDUNE has everything you need to send Transactional and Marketing emails at scale .... Contact Management, Email Designer, Template Management, Automations, Analytics, Reputation Management (SPF + DMARC + DKIM). **EVERYTHING**. Just connect your AWS Account to [get started](https://docs.sendune.com/get-started). ### Why use SENDUNE? If you are a Startup, chances are your entire tech stack is on AWS but you are not using [AWS SES](https://aws.amazon.com/ses/). Instead you use a third party email service like Mailchimp or SendGrid. There's only two things that matter when it comes to email. **Deliverability** and **Cost**. Lets break down each of these. #### **1. Email Deliverability.** Every **Email Service Provider (ESP)** claims to have the best deliverability. These statements are misleading. Let's talk about this a bit. Email is a decentralised system. Every ESP is like a separate country. Just like every country gets to decide who they let in, every ESP gets to decide which email to receive and what to do with it (like send to inbox or send to junk). It means that the Sending ESP has zero control over the Receiving ESP. So any statements guaranteeing email deliverability are bunk. A well governed ESP, just like a well governed country, adheres to some rules and thereby builds a reputation. It is this reputation that allows the frictionless exchange of emails (i.e. deliverability). So how do things work? Email deliverability and inbox placement are a function of two things. * **Adhering to industry standards (DMARC, DKIM, SPF, etc):** All reputed ESP's, including SENDUNE, give you the tools to adhere to industry standards. In fact SENDUNE insisted on these standards from the very start (early 2018), [much before](https://x.com/SendWithSES/status/1752737377943224479) they became mandatory. Adhering to these standards is like getting a 'visa-on-arrival' to another ESP. So deliverability comes down to the content of your email. * **The content of your email:** Email is a 'Receivers' prerogative, not the 'Senders'. If you are sending unsolicited emails, the pedigree of your ESP cannot help you in any way. In fact every ESP including SENDUNE will kick spammers out without a moments hesitation. **Deliverability Conclusion:** SENDUNE gives you the same deliverability as any other ESP. #### 2. Email Cost. Every company - no matter the size or stage - needs a mix of transactional and marketing emails. Usually this mix is about 20% transactional and 80% marketing emails. Let's consider the email requirements for three types of organisations. * **Startup** (5000 Users + 15000 Emails) * **SME** (50000 Users + 150000 Emails) * **Large Enterprise** (500000 Users + 1500000 Emails) The following table compares the lowest monthly plan cost, in US Dollars, of different ESP's. Prices are as on 27-Aug-2024. | ESP | Startup | SME | Large Enterprise | | ------------------------------------------------------------------ | ------- | ------- | ----------------------- | | [AWS SES](https://calculator.aws/#/createCalculator/SES) | $ 2 | $ 18 | $ 180 | | [SENDUNE](https://sendune.com/pages/pricing) + AWS SES | $ 2 | $ 42 | Enterprise (\~ $ 500 +) | | [Sendgrid](https://sendgrid.com/en-us/pricing) | $ 35 + | $ 140 + | Contact them | | [Mailchimp](https://mailchimp.com/pricing/marketing/?currency=USD) | $ 90 + | $ 312 + | Contact them | | [Resend](https://resend.com/pricing) | $ 60+ | $ 270 + | Contact them | **Cost Conclusion:** SENDUNE is the undisputed winner if you want a [full fledged](https://sendune.com/pages/features) platform with contact and template management, workflows, team management with role based access, etc. If you are just sending a few uncomplicated emails, AWS SES is the best option for you. Need help? Talk to us - **hello at sendune dot com**. # Open Source Open source HTML email editor and designer. The core of [SENDUNE](https://sendune.com/) is the email template designer. It lets you create and save templates that you can use to send emails manually or via the API. * The source code is available on [Github](https://github.com/SendWithSES) under the MIT license. * A demo is available here: HTML for email is probably the hardest code to write. Even a teeny-tiny deviation from the rules will break the email in untold combination of os/desktop/mobile clients.\ \ It's mid 2024. Almost 50 years since email was invented and 35 years since HTML was born. A 'basic-open-source-HTML-email-designer' must be a solved problem, right? We thought so too.\ \ Sadly, that's not the case.\ \ There are a few decent open source email designers but they carry dependencies that make them cumbersome to embed within your app. That's why we decided to open source our HTML Email Designer.\ \ The SENDUNE email designer focuses on simplicity and ease of use. It is light-weight. It does pure HTML - no intermediate code wranglers like mjml. There is no lock-in of any kind. Save HTML output as a template and use with ANY email service provider.\ \ Feel free to fork the repository, make improvements, and submit pull requests. ### ⁉️ Why Choose SENDUNE Email Designer? * **Truly Open Source:** Use it for personal use or commercial use or whatever. * **Truly Free:** Because the ones that say 'free', are not. * **Truly Works:** Because the ones that are free don't seem to work. * **Truly HTML:** No intermediate code wranglers like mjml. * **Truly Fast and Light Weight:** Because you have better things to do with your time. * **Truly No-Code:** Design like a pro without coding headaches. Our minimal interface gets out of your way. * **Truly Democratic:** Save HTML output as a template and use with ANY email service provider. ### 3️⃣ Three Ways To Create Templates Comes with three template types that let you design any kind of transactional or marketing emails. Altogther, you can create and save unlimited templates. * **Drag and Drop Designer** - Start designing beautiful emails immediately. * **HTML Code Editor** - Reuse HTML templates that you already have or code them from scratch. * **Plain Text Emails** - 'Minimalists'. This is for you. ### 🚀 Built On Solid Fundamentals. Follows a few fundamental rules to design emails that work in nearly all email clients (web and mobile). It is built upon some great work done by these people. * Ted Goas - * Nicole Merlin - * Mark Robbins - ### 🎪 Live Demo. Play around with the live demo at [https://designer.sendune.com](https://designer.sendune.com/). You can design a template and send yourself a test email. ### 👩‍💻 Installation Install via NPM: ``` npm install @send-with-ses/ng-email-designer ``` Or via YARN: ``` yarn add @send-with-ses/ng-email-designer ``` ### 🖼️ Image Handling You can use a cloud storage of your choice (ex: AWS S3, Cloudflare R2, GCP Cloud Storage etc) for storing your images. Please implement your image upload functionality and provide it to the library as below (imageUploadTriggered/imageSelectionTriggered). ``` ``` [Click here](https://www.npmjs.com/package/@send-with-ses/ng-email-designer) for more documentation ### 🎨 UI Theming and Styles You can make a few changes to make the Email Designer match your website colors.\ \ Import the following styles into your global styles file (e.g., styles.scss): ``` @import '../node_modules/email-designer/src/lib/theme.scss'; @import '../node_modules/email-designer/src/lib/email-editor.css'; ``` To make the Email Designer match your website's UI, include the following in your main.scss or styles.scss file and change the colors as you like. ``` :root { --sws-icon-color: #ccc; --sws-icon-hover-color: #555; --sws-header-background: #eee; --sws-header-text-color: #555; --sws-border-color: #ccc; } ``` ### 🤝 Contribute. Feel free to fork the repository, make improvements, and submit pull requests. ### 🐛 Issues or Ideas. Spotted a bug or got an idea? Just open an issue or write to designer at sendwithses dot org. \ \- - - - - - - - - - - - - - SENDUNE open source HTML editor and template builder. Available on Github. MIT license. [![Featured on Hacker News](https://hackerbadge.now.sh/api?id=41007403)](https://news.ycombinator.com/item?id=41007403) # Get Started Setup your SENDUNE integration with AWS SES. ## Before You Start SENDUNE integrates with your AWS Account to send Transactional and Marketing Emails at scale. ## Getting Started When you log in to SENDUNE for the first time, you are taken to the 'Settings' page. There are five steps you need to fulfill. Once these steps are done you need to [raise support tickets](#id-6.-move-out-of-ses-and-sms-sandboxes) with AWS to get your SES and SMS accounts out of the sandbox and into production mode. The whole process can take upto 30 minutes (much lesser if you are familiar with AWS). If you do not have the time, you can STOP HERE. If you do have the patience, SENDUNE offers you everything you would expect from any reputed email service provider - minus the high cost and complexity.

### 1. Select Primary Key The 'Primary Key' is the way you uniquely identify your users. This is usually the **Email ID** or **Mobile Number** with which your users log in to your app or website. Choose one accordingly. This cannot be changed once set. ### 2. Select AWS Region AWS has datacenters in many regions. SENDUNE currently supports the below three regions only. * US East (N. Virginia) * US West (Oregon) * EU (Ireland) Select any one that suits your requirement. All your email and sms sending is done from this region. Remember your selection because all your AWS support requests (for moving out of SES sandbox, raising sending limits, etc.) must be made from this region. ### 3. **Enter AWS IAM Role ARN** You need to create an ARN Role in your AWS account and add it in the SENDUNE dashboard. This allows SENDUNE to programmatically connect to your AWS account to perform various actions like sending emails and sms. Please note that as of now SENDUNE requires the 'IAMFULLACCESS' Role. Here's [why](https://docs.sendune.com/setups#must-read-why-we-ask-for-iam-full-access-role). Follow step-by-step instructions below to create the ARN Role. **3.1** Sign in to your AWS account and go to the IAM section.

**3.2** Select 'Role' from the side panel and click 'Create role'.

**3.3** Follow the instructions as shown in below image to the dot. {% hint style="danger" %} **IMPORTANT**: When creating AWS Role, the 'Account ID' to be mentioned is **033267325636**. {% endhint %}

**3.4** Search for 'iamfull' and check the box beside 'IAMFullAccess'. Click 'Next'.

**3.5** Type in details as shown in below image and click 'Create role'. Your Role

**3.6** Select the Role that has been created.

**3.7** Copy the Role ID.

**3.8** Paste the Role ID in SENDUNE settings dashboard and click 'Verify'. It might take a few seconds to verify your Role. Refresh browser and try again if verification does not work the first time.

**3.9** Success. Your Role is verified. Your AWS account is now successfully connected to SENDUNE. You can proceed to the domain verification step.

### **4. Enter Domain To be Verified** This is the domain from which you will be sending your emails. We recommend you use a sub domain (Ex: emails.yourdomain.com) rather than your root domain. ### **5. Enter DNS Records** Once you enter your domain, you will be shown a set of DNS records. You will need to enter these DNS records with your domain registrar. It can take a few hours (usually much lesser) before your DNS records are verified. The DNS records are related to DMARC, DKIM, and SPF protocols which protect your domain from spammers, phishers, and other unauthorized parties. Most importantly they create trust and prevent your emails from landing in spam folders. ### 6. Move out of SES sandbox. One last step before you can put all this behind you - getting your SES accounts out of the sandbox and into production mode. {% tabs %} {% tab title="6.1 Move out of SES Sandbox." %} To prevent abuse AWS puts new accounts in '[Sandbox Mode](https://docs.aws.amazon.com/ses/latest/DeveloperGuide/request-production-access.html)' with certain restrictions. You need to raise a ticket with AWS to move out of the SES Sandbox. Make sure you have completed ALL the five steps above. Only then proceed with the step-by-step instructions below. 1. Login to your AWS account. Search for 'SES' and go to the Simple Email Service dashboard.

2. Click the the dropdown at the top-right. Select the AWS region from which you want to send emails. This must be the same region that you have selected in your SENDUNE settings dashboard (i.e. [Step-2](#id-2.-select-aws-region) above).

3. Click '**Get set up**' from left panel and then click '**Request production access**'.

4. Choose the type of emails you want to send, 'Marketing' or 'Transactional'. Enter the same domain or sub-domain that you have entered in your SENDUNE settings dashboard (i.e. [Step-4](#id-4.-enter-domain-to-be-verified) above). Accept terms and submit request. It is VERY IMPORTANT that the domain you enter here have an active website that showcases the nature of your business. AWS might reject your request if you do not have a website or just have a generic landing page.

5. That's it. You can sit back and relax. If everything is in order AWS will move your SES account into production and you will be able to send emails. It might take upto a day before AWS grants your request. Occasionally AWS might send you an email asking for more details. Reply with as much detail as possible. You must be able to convince AWS that you are a genuine email sender.

6. You will receive an email once AWS moves your SES account out of the sandbox. You can also click '**Account dashboard**' from the left panel and see your sending limits. For new accounts AWS grants a sending limit of 50,000 emails er day with a sending rate of 14 emails per second.

7. If you need more you can always raise a request to increase your limits.

8. You can request a raise for your '**Sending quota'.**

9. You can also request a raise for your '**Sending rate'**.

10. And finally, keep an eye on your sending reputation. You can find this by clicking '**Reputation metrics**' in the SES dashboard. Make sure your reputation is always 'Healthy'. AWS will block your account if you send unsolicited emails. These blocks are usually permanent. The block is not only for your AWS account but also for your domain.

{% endtab %} {% endtabs %} WONDERFUL. If you have come this far, GREAT WORK. Your SENDUNE account is now ready to use. \======== **Notes** ======== {% hint style="danger" %} ### **MUST READ: Why we ask for "IAM Full Access" Role ?** In the early days of SENDUNE, we asked full access permission only for SES and SNS. SENDUNE is in a constant state of development. As we kept building the product we wanted permissions for S3 to store email images and SQS to queue email delivery notifications for further processing. Sometime later we wanted CloudWatch access to hold and process SMS related delivery notifications. We also expected AWS to introduce breaking changes and wanted to be ready in such cases. Not surprisingly AWS sent everyone the following message a few months ago. (They later rolled backed on this requirement.) *"We are reaching out to notify you that AWS Managed Policy is making a change that will require your action. AWS Managed Policy is deprecating the managed policy "CloudWatchFullAccess" and replacing it with "CloudWatchFullAccessV2". After December 7, 2023, "CloudWatchFullAccess" will no longer be supported."* How do we provide an uninterrupted and seamless experience to end users when we have to constantly keep asking them to add specific permissions every now and then. This was not at all user friendly. Both end-user experience as well as product development suffered. So we decided to ask only for one permission - IAM Full Access. Some people were/are unhappy. Somehow their assumption was, "*If we give you IAM Full Access you will misuse it.*", or, "*Your servers will get hacked and those hackers will do something bad.*" Understandably, these are valid assumptions, like, "*Do not build a flying machine because it might crash.*" We believe transparency and a proper explanation will convince some people and no amount of explanation will convince other people. To those people who are considering to use SENDUNE, this is how we handle things. 1. SENDUNE accesses your AWS Account by requesting a set of temporary keys using the 'IAM Role' provided by you. This is the recommended best practice by AWS. No third parties can access your account. 2. IAM Full Access is something similar to full admin access. It gives SENDUNE the power to provision any resource within your AWS Account. However SENDUNE only provisions resources which are required. Currently these are - SES, SQS, SNS, S3, Pinpoint, CloudWatch. 3. You can delete the IAM Role at any time to prevent SENDUNE from accessing your AWS Account. 4. **It is highly recommended you create a separate AWS Account exclusively for SENDUNE. This way you can be sure that any resource launched within this AWS Account has been provisioned by SENDUNE.** {% endhint %} # Contacts The Contacts module is the default landing page in SENDUNE. Each of your contact is represented by their Email ID or Mobile Number. You can add contacts manually or via the API or by importing a [CSV file](https://docs.google.com/spreadsheets/d/1Xoe7dAPyMSjoiZKAPTf43RbUO_LRSBmjDeFD2JixXjM/edit?usp=sharing). The contacts module in SENDUNE is very powerful and can scale to hold billions of contact metadata points. The easiest (and recommended) way to is to attach 'tags' to contacts. For example, if a user adds 'purple pants' to their wish-list, you attach the tag 'purple pants' to that user. You can then slice-n-dice this data to generate your own 'intelligence' and send targeted messages. ### **SENDUNE Contacts API** The '**add-contact**' API is a simple, language agnostic, cURL request. It is used to add/update contacts as well as to attach/detach tags.

Click **User+** icon at top right in SENDUNE dashboard to get this popup.

{% tabs %} {% tab title="API Request" %}

URL: https://api.sendune.com/add-contact

``` { "method": "POST", "url": "https://api.sendune.com/add-contact", "headers": {"template-key": "*****************************zkLG"}, "body": { "email": "example@gmail.com", "status": "Unsubscribe", "full_name": "John Due", "mobile": "+918098763849", "dob": "10-10-1990", "gender": "Male", "city": "Hyderabad", "country": "India", "add_tags": "aaa,bbb,ccc", "remove_tags": "ddd,eee,fff" } } ``` **IMPORTANT:** * All API calls MUST include the **Contact Upload Secret Key**. * All API calls MUST include the '**Primary Key**' of the contact. Primary Key is used to uniquely identify a contact in the database. This is either the Email or the Mobile Number of your end user. * Mobile numbers must strictly be in [**E.164**](https://help.twilio.com/articles/223183008-Formatting-International-Phone-Numbers) format. (Example: +442071838750). {% endtab %} {% tab title="API Response" %} Success Response: {% code lineNumbers="true" %} ``` { "success": true, "message": "Contact added" } ``` {% endcode %} Failed Response: {% code lineNumbers="true" %} ``` { "success": false, "message": "message details", "error": "error details" } ``` {% endcode %} {% endtab %} {% endtabs %} ### Rate Limits Rate limits apply to the Contacts API (add-contact) endpoint as per the below table.

Plan	Rate Limit (requests/minute)
Free	60
Paid	1,800 (Soft Limit)
Enterprise	Upto 60,000

To illustrate, the 'Paid Plan' has a rate limit of 1800 requests/minute. This lets you call the SENDUNE Contacts API 30 times per second or do a single burst of 1800 calls in one second or anywhere in between. The sum total of all API calls must not exceed 1800 in one minute. API rate limit is a soft limit for paid plans, meaning you can do occasional short bursts that exceed the rate limit as long as you are not abusing our systems. {% hint style="success" %} #### **IMPORTANT NOTE** Rate limits apply only to the Contacts API (**add-contact**) endpoint. API rate limits do not apply to the Email, SMS, OTP endpoints. Email/SMS sending rates are determined by AWS. For example, if your AWS SES email sending rate is 250/second, you can call the '**send-email**' endpoint up to 250 times per second - even if you are on the 'Free Plan'. {% endhint %} ### Contact Ratings Every new Contact (User) added to SENDUNE starts with a 2 star rating. Depending on the way the Contact interacts with your emails (opens, clicks, etc), the rating goes up or down. If a Contact regularly opens your emails and clicks (engages) with them, the rating goes up. If a Contact marks your email as spam or unsubscribes, their rating becomes 1 and they are no longer sent emails. Contact ratings help you understand who among of your Contacts are loyal to your brand and and who are not. This helps you design your communication strategies. Contact ratings also help keep you email list clean and protect your domain reputation. # Email **SENDUNE** integrates with your AWS SES account to send emails. You can send both Transactional and Marketing emails. You must create a template for each kind of email you wish to send. ### **Create Email Templates** Click the '**Send**' button at the top to open the email composer (see video below). There are three template categories. You can create as many templates as you wish within each category. * **SENDUNE Designer**: A visual editor that makes it very easy to design emails. * **HTML Editor**: Use this if want to code your own emails. If you have purchased any HTML template, you can copy-paste that code in the HTML Editor. * **Plain Text**: This is as simple as it gets. Use it compose plain text emails just like you do in Gmail or Outlook. Though they look simple, plain text emails perform very well. {% embed url="" %} Once your templates are ready you can use them to send emails manually, via the API, or via automated rules (workflows). Remember to send yourself a '**Test Mail**' to make sure your template looks good. ### **Manual Email** Use this option to send marketing emails to multiple users. To send an email manually, select one or more contacts, choose a template (or compose a new one) and click '**Send**'. Once the emails are sent you can view delivery statistics. See video below. {% embed url="" %} ### **API Email** This is used to send transactional emails. The '**send-email'** API is a simple, language agnostic, cURL request. Every email template you create comes with a 'Template Key'. Use this key in the cURL request to programmatically send emails. Click the '**API**' button at the top right of the email composer to find the template key. {% embed url="" %} {% tabs %} {% tab title="API Request" %}

URL: https://api.sendune.com/send-email

{% code lineNumbers="true" %} ``` { "method": "POST", "url": "https://api.sendune.com/send-email", "headers": {"template-key": "***********************HOcm"}, "body": { "email": "example@gmail.com", "subject": "Subject", "this-is-a-replace-tag": "Value" } } ``` {% endcode %} **IMPORTANT:** * All API calls MUST include the **Template Key**. * Template Key is unique to each email template you create. * Template keys are secrets and must not be used on the client side. {% endtab %} {% tab title="API Response" %} Success Response: {% code lineNumbers="true" %} ``` { "success": true, "message": "Email Sent" } ``` {% endcode %} Failed Response: {% code lineNumbers="true" %} ``` { "success": false, "message": "message details", "error": "error details" } ``` {% endcode %} {% endtab %} {% endtabs %} ### **Replace Tags (Merge Tags)** You can use Replace Tags (aka, Merge Tags) when composing API emails. There are two types of replace tags. * **Standard Replace Tags:** This is indicated by a unique name within double-curly-brackets, like ... **{{password-reset-link}}**. When sending email, the content within the double-curly-brackets will be replaced by the content you send via your API call. * **Name Replace Tag:** You generally use this to send personalised emails to your users. This is a special kind of replace tag that must be STRICTLY written as **\[\[name]]** - 'name' in lower case in double square brackets. The **\[\[name]]** in your email template is replaced with the **Full Name** associated with your Contact. ### Workflow Email Emails can be automated based on **'if-this-then-that'** rules. See this [section](/email-automation) for more details. ### \*\* IMPORTANT READING \*\* {% hint style="danger" %} ### **Warming up your email account** New email accounts that immediately start blasting off a huge volume of emails will trigger spam filters at email service providers (Gmail, Yahoo, Outlook). Once your domain or IP address is flagged as a spammer, it is almost impossible to shake off that reputation. Every account on SENDUNE is automatically enrolled in the [InboxVISA](https://sendune.com/pages/inboxvisa) program - a collection of email sending best practices and real-time heuristics adopted by SENDUNE to protect you and guide emails safely into user inboxes. While these practices create trust with email service providers, the final decider in inbox placement is the content of your email. Ultimately, the only one who can guarantee safe inbox placement is YOU. Here are some steps we HIGHLY RECOMMEND you follow in order to warm up your email account. ### Week 1 1. **Send a Few Emails Initially:** Start by sending a small number of emails (10-15 per day) to friends, colleagues, or yourself. 2. **Personalize Your Emails:** Make sure your emails are personalized and relevant to the recipients. Do not use ALL CAPS subject lines, excessive punctuation, or clickbait headlines. 3. **Monitor These Initial Emails:** Many email service providers randomly send the first few emails into spam folders. Look out for such emails and mark them as 'Not Spam'. ### Week 2 1. **Increase Volume Gradually:** Slowly increase the number of emails you send each day by 10-20% every few days. Avoid sudden spikes in volume. 2. **Monitor Engagement:** Track open rates, click rates, and responses. Adjust your sending volume and email content based on the engagement you receive. ### Week 3 Onwards By now your email account would have been sufficiently warmed up. You must still follow these best practices to maintain your reputation. 1. **Send Relevant Content:** Always ensure your emails are relevant and valuable to your recipients. 2. **Stay Consistent:** Maintain a consistent sending schedule to build trust with email service providers. {% endhint %} # SMS WIP **SENDUNE** integrates with your AWS SNS account to send SMS (Text Messages). You can send SMS manually, via the API, or via automated rules (workflows). ### **Manual SMS** To send SMS manually, go to the 'SMS > Manual' tab, select one or more contacts and click "Send" button at the top. You will be shown a popup where you can compose your SMS. See video for demo. {% embed url="" %} {% hint style="info" %} **NOTEs:** * Sender ID is optional. Enter only if you have one. * Origination number is required only if you are sending to USA mobile numbers. {% endhint %} ### **API SMS** Use this to send Transactional SMS. See the request/response details below. {% embed url="" %} {% tabs %} {% tab title="API Request" %}

URL: https://api.sendune.com/send-sms

{% code lineNumbers="true" %} ``` { "method": "POST", "url": "https://api.sendune.com/send-sms", "headers": {"template-key": "**************************4lVm"}, "body": { "sender_id": "ABCDEF", "origination_number": "+449876543212", "mobile": "+449876543210", "message": "Hello John." } } ``` {% endcode %} **IMPORTANT:** * All API calls MUST include the **Template Key**. Template Key is unique to Transactional SMS and Marketing SMS. * 'Origination Number' is required only when sending to USA mobile numbers. * All mobile numbers MUST be in E.164 format. {% endtab %} {% tab title="API Response" %} Success Response: {% code lineNumbers="true" %} ``` { "success": true, "message": "SMS Sent" } ``` {% endcode %} Failed Response: {% code lineNumbers="true" %} ``` { "success": false, "message": "message details", "error": "error details" } ``` {% endcode %} {% endtab %} {% endtabs %} ### **Workflow SMS** See '[Automation](/email-automation)' section for more details. # OTP **One Time Password** (**OTP )** is a special type of Transactional SMS (Text Message). OTP's are used to send one time codes intended for Login or Two-Factor Authentication (2FA) or other high value transactions. OTP SMS has a template that allows you to customise fields like App Name, OTP Size, and OTP Expiry Time. {% embed url="" %} The OTP SMS has two parts, ***Send API*** and ***Verify API***. {% tabs %} {% tab title="Send API" %} Send API is used to trigger the SMS containing one time code to the end user. ``` URL: https://api.sendune.com/send-otp ``` **Request:** {% code lineNumbers="true" %} ``` { "method": "POST", "url": "https://api.sendune.com/send-otp", "headers": {"template-key": "****************************elA2"}, "body": { "sender_id": "ABCDEF" "origination_number": "+449876543212" "mobile": "+449876543210", } } ``` {% endcode %} **Success Response:** ``` { "success": true, "message": "OTP Sent" } ``` **Failed Response:** {% code lineNumbers="true" %} ``` { "success": false, "message": "message details", "error": "error details" } ``` {% endcode %} **IMPORTANT:** * All API calls MUST include the **Template Key**. Template Key is unique to OTP SMS. * 'Origination Number' is required only when sending to USA mobile numbers. * All mobile numbers MUST STRICTLY be in E.164 format. {% endtab %} {% tab title="Verify API" %} Verify API is used to match the one time code received from end user with the code generated during the Send API call. ``` URL: https://api.sendune.com/verify-otp ``` **Request:** {% code lineNumbers="true" %} ``` { "method": "POST", "url": "https://api.sendune.com/verify-otp", "headers": {"template-key": "***********************elA2"}, "body": { "mobile": "+449876543210" "otp": "123456", } } ``` {% endcode %} **Success Response:** {% code lineNumbers="true" %} ``` { "success": true, "message": "OTP Verified" } ``` {% endcode %} **Failed Response:** {% code lineNumbers="true" %} ``` { "success": false, "message": "message details", "error": "error details" } ``` {% endcode %} **IMPORTANT:** * All API calls MUST include the **Template Key**. Template Key is unique to OTP SMS. * 'Origination Number' is required only when sending to USA mobile numbers. * All mobile numbers MUST STRICTLY be in E.164 format. {% endtab %} {% endtabs %} # API Reference Every API call in SENDUNE is a simple, language agnostic, cURL request. SENDUNE does not publish integration libraries for any programming languages. You do not have to embed or update or maintain any of our code within your code. This is in line with our [first principles](/why). ### Base URL ``` https://api.sendune.com ``` The Base URL is followed by the endpoint you wish to call. Every API call must include the relevant 'secret key'. The base URL accepts only **HTTPS** traffic. **HTTP** is rejected. ## There are four API endpoints. ### 1. Contacts API The '**add-contact**' endpoint is is used to add/update contacts. {% tabs %} {% tab title="API Request" %}

https://api.sendune.com/add-contact

``` { "method": "POST", "url": "https://api.sendune.com/add-contact", "headers": {"template-key": "*****************************zkLG"}, "body": { "email": "example@gmail.com", "status": "Unsubscribe", "full_name": "John Due", "mobile": "+918098763849", "dob": "10-10-1990", "gender": "Male", "city": "Hyderabad", "country": "India", "add_tags": "aaa,bbb,ccc", "remove_tags": "ddd,eee,fff" } } ``` **IMPORTANT:** * The API call MUST include the **Contact Upload Secret Key**. * The API call MUST include the '**Primary Key**' of the contact. Primary Key is used to uniquely identify a contact in the database. This is either the Email or the Mobile Number of your end user. * Mobile numbers must strictly be in [**E.164**](https://help.twilio.com/articles/223183008-Formatting-International-Phone-Numbers) format. (Example: +442071838750). {% endtab %} {% tab title="API Response" %} Success Response: {% code lineNumbers="true" %} ``` { "success": true, "message": "Contact added" } ``` {% endcode %} Failed Response: {% code lineNumbers="true" %} ``` { "success": false, "message": "message details", "error": "error details" } ``` {% endcode %} {% endtab %} {% endtabs %} ### 2. Email API The '**send-email**' endpoint is used to send transactional emails. Every email template you create comes with a 'Template Key' which must be used in the cURL request. {% tabs %} {% tab title="API Request" %}

https://api.sendune.com/send-email

Plan	Rate Limit (requests/minute)
Free	60
Paid	1,800 (Soft Limit)
Enterprise	Upto 60,000

# InboxVISA™ {% hint style="success" %} #### All SENDUNE users (Free and Paid) are automatically enrolled in the InboxVISA program. {% endhint %} InboxVISA™ is a collection of email sending best practices and real-time heuristics adopted by SENDUNE to protect all users and guide emails safely into user inboxes. While these practices create trust with email service providers, the final decider in inbox placement is the content of your email. Ultimately, the only one who can guarantee safe inbox placement is YOU. Some practices adopted by InboxVISA are; 1. SENDUNE forces some industry standard best practices upon you like having a domain with SPF, DMARC, DKIM records in place before you can send emails. 2. Delivery stats for every email you send are monitored and this collective intelligence is used to generate insights. For example, if messages to 'GMAIL.COM' ESP have a lower CTR compared to other ESP's, this could mean your emails are landing in GMAIL spam folders. 3. SENDUNE maintains a Central Bounce Register (CBR). This is a list of email addresses that have resulted in a hard bounce in the recent past. Messages are not delivered to emails in the CBR. This helps you stay within acceptable bounce limits and maintain your reputation with ESP's. 4. SENDUNE monitors SBUR (Spam + Bounce + Unsubscribe + Reject) rate for all accounts in near real-time. Accounts with SBUR >=5% are banned. This helps weed out bad actors from the platform thereby protecting genuine users. The purpose of InboxVISA is to protect genuine users from making inadvertent mistakes. InboxVISA cannot help you if you are sending unsolicited messages.
# Customer Support Popup The Customer Support Popup is a simple widget that you can embed in your website. This is a great alternative to 'Live Chat' plugins. When visitors to your website enter a message it will be forwarded to an email destination of your choice where you can reply and handle customer support. The Customer Support Popup is available in the Settings page. You can design it a bit to suit the theme of your website.

To embed the Customer Support Popup paste the code between the `` and `` tags of your website as shown in example below. ``` This is the head of your page Example HTML page This is the body of your page. ``` The 'Customer Support Popup' shows up at the bottom-right of your website like below.

# Delivery Stats Delivery statistics for every Email and Workflow are tracked individually and in aggregate. Keep an eye on these stats because they form the basis on which your sending reputation is calculated. You risk being banned if your SBUR (Spam, Bounce, Unsubscribe, Reject) Rate is >=5%

SENDUNE's [InboxVISA](https://sendune.com/inboxvisa) uses these stats to monitor your reputation in realtime and protect you from make inadvertent mistakes. # Audit Logs wip # Team Management wip # Team Inbox Launching soon.