Email to/from SMS¶
Documentation of how to send emails to sms and using web hooks to receive messages and have them delivered to your email inbox.
Email to SMS¶
To use this API, you need to whitelist one or more emails or an entire domain, for sending smses.
To whitelist emails and domains go to “Settings” “Email Whitelist”, add an email like firstname.lastname@example.org or an entire domain e.g. @example.com if your whole organisation should be able to send messages this way.
If you whitelist @example.com no other accounts will be able to use this domain.
To successfully deliver your email as a SMS you have two options for proper authentication:
- Your whitelisted emails or domain, need to pass SPF check and have a DKIM record.
- You need to put an API token in the Subject field of the e-mail.
For security reasons we highly recommend option 1, since e-mails in most cases are transferred unencrypted over SMTP, an attacker might be able to capture your API tokens. We do provide the second option for customers that are unable to setup SPF and DKIM for their e-mail.
If you use API token and you also use our IP whitelist, then you will need to whitelist the IP-address of your outgoing e-mail server as well.
Sending an SMS¶
Sending via the Email to SMS api is straightforward, all you need to do is send to the phonenumbers of your recipients and set a default sender id.
Your sender ID is controlled by the default sender setting found under “Settings”, “SMS defaults”.
Smses send on this API is limited to 5 sms parts, equal to 765 characters, this is a measure to try and prevent unintenionally long smses send, when using email clients like e.g. Gmail, where the mails are kept as conversation threads, where responding to the original email, will keep the entrie conversation in the email.
SMS to Email¶
Receiving SMS messages from your users in your email inbox, requires you to have a virtual number attached to your account, and to use this number with a SMS to Email web hook.