Setup sending gateway by providing API details of your account. MumaraSMS offers integration with more than a few industry leading sending gateways like Infobip, Twililo and Clickatell etc. To setup one of the available gateways with MumaraSMS, you need to have your account created with the particular gateway that you want to use for sending. Every company may require different details to authenticate the incoming API request and to connect with its gateway. Therefore, you will notice that some of the fields dynamically change when you select the “Company Name” from the first dropdown. Let’s see how it works.
Navigate to Setup Gateway
Admin Main Navigation->Setup->Gateways->Setup Gateway
Required Details to Setup API
Company Name (Dropdown Options)
Dropdown offers list of all gateways application is currently integrated with, i.e. Clickatell, Infobip, Twilio etc. You need to click on desired company’s gateway to open up relevant fields below.
Following area discusses the fields that you need to fill with appropriate information in order to setup Infobip’s sending gateway.
Infobip allows creating a unique API key as one of the requirement to authenticate the API request. Provide that particular API key in this field.
Secret key is another required parameter that infobip requires as authorization token to accept an API request. Put forward your infobip account’s secret key in this field.
Select your preferred pattern of sending SMS from the specific gateway, the dropdown has two options. Sending pattern largely depends on how the gateway accepts sending request from the application side. For example, MumaraSMS only offers batch options when the selected gateway permits accepting the batch of contacts and further process sending in batch.
- Batches- When selected, MumaraSMS will collect number of contacts suggested for a batch, and will supply the batch of contacts to the gateway for sending. When you select “Batches” as preferred pattern of sending, a field will appear underneath to select the suitable size of the batches.
- Loop- For this option, system processes sending of the messages one by one.
Select “Active” to mark the status of the specific gateway as active and working. System will only use Gateways with Active status for sending. And if you don’t want to send from this gateway right now, you can mark the status of the gateway as “Inactive”.
Fallback Sender ID
In case if primarily preferred Sender-ID fails, system automatically shifts to the Sender-ID you will set as alternative in this “Fallback Sender ID” field. Primarily preferred Sender-ID can be the one that client has got approved for the sending, or the one that is given as application’s Default Sender-ID for the clients who don’t have their own Sender-ID approved. In case of the failure, system automatically shifts to the Fallback Sender-ID.
Image#MS-5.6.1: Setting Up Infobip
Most of the system required fields such as Name, Status, Fallback Sender-ID and Sending Pattern etc. will remain the same for every sending gateway; except for few unique fields that gateway requires to authorize API request and connect. So in case of setting up Clickatell API, following are the fields different than other gateways.
Unlike the API key of Infobip, Clickatell requires account username and password to authorize and connect. Provide the username of your account with Clickatell account and proceed.
Provide password of your Clickatell account in this field.
As mentioned, rest of the fields will remain and work the same as mentioned above.
Image#MS-5.6.2: Setting up Clickatell
With Twilio, following are the two parameters that Twilio take into consideration to determine on the account from which the API request is initiated. Make sure, Twilio doesn’t allow sending in batches, therefore, you will only have the option of sending in loop.
For sending API request, Twilio requires providing two important credentials; the first one is the account SID which acts like username of your account. Provide your Twilio account SID here in this field.
Auth Token is like the password to the SID that you have just provided in the field above. Anyone without knowing this combination of valid SID and Auth Token will not be able to get the API request authorized by Twilio.
Image#MS-5.6.3: Setting up Twilio