Postways is a Message Management System for Transactional Messages. the goal of Postways is to allow you to specify messages independently from the infrastructure over which these messages are send. With Postways you define a default template, customize it for specific channels such as email, SMS and mobile push, and then when the message is send, it will be composed correctly for each of those channels respectively.
You can think of Postways as a higher level of abstraction to existing email, SMS and mobile push notification API's with the difference that Postways has a focus on the message, rather than the infrastructure over which the message is send.
Before you get started sending messages through Postways you might want to configure some default settings first. On the Settings page there are two important fields that you want to maked sure are filled out since it will you save some time in figuring out why emails might fail to be send.
To be able to send any type of messages through Postways you are required to bring your own means of transport. E.g. to send emails, Postways supports integration with Amazon SES. However, for Amazon SES to function properly you need to do make sure of the following;
- Make sure you verify in SES the email address from which your application sends emails.
- Make sure that in Postways you have specified an SES verified email address as the Default From Email.
The Default From Name will by default be set to your team name. This field is used as the Sender Name when Postways sends out messages, i.e. the name of the product of service that recipients of the message will see. E.g. when you send an email through Postways and the From Name is set to "My Team" then recipients of a message will see an email from "My Team" in their inbox. In a template you can override this value but it's likely to be the same for most templates.
The Default From Email is the default email address from which Postways will send emails. Together with the Default From Name, in the case of emails, this field will be the email address of the sender (your service or product). E.g. if your Default From Email is
firstname.lastname@example.org then the sender of an email will become
My Team <email@example.com> which is what recipients will see in their inbox.
When you have signed up for Postways and you want to start sending messages, it's required that you set up a 3rd party integration under the Integrations menu. For Postways to actually send messages you need bring your own means of transport. Currently Postways fully support Amazon AWS SES and SNS for sending email, mobile text (SMS) and mobile push (for Android and iOS).
Please refer to the Developer Guide for more information on setting up your AWS integration.
When you use Postways you will notice that we often refer to transmissions and messages. But what exacly are transmissions and how are they different from messages?
Postways allows you to send messages over different channels. A channel can be email, SMS or mobile push. Within a template you define the channels over which a message can be send. For some templates this can be more than one channel. E.g. within a template you can define that you prefer to send a message as a mobile text message (SMS) and that you always require to send it as an email. In the template settings these are the Preferred and Required channel settings.
When your application calls the Postways
/transmissions API endpoint to send a message, you are required to provide a list of one or more recipients. For each recipient you can specifiy up to three different targets;
push. If e.g, a template has been configured in the Requried Channels to send both an SMS and an email and for a recipient both a phone number and an email address is specified, then both an SMS and email will be sent. This means that with one transmission, two messages were send. If the phone target for the recipient was empty or not specified, a mobile text could not have been sent. In that scenario only the email would have been sent.
A good strategy for calling the Postways
/transmissions API is to always supply all the details you have in regards to a recipient. By doing this it means that you move the control over which channels a message can be send to Postways, making it easier to control the flow and to simply your application logic.