6a9ee0611d3181788797025.png

How to Set Up an SMS API Gateway and Send Bulk SMS

Libwana.net allows you to connect an SMS provider and send SMS messages directly from your account. You can configure a supported Built-in API provider or connect another SMS service using the Custom API option.

Once your SMS API Gateway is configured and enabled, you can send SMS messages to a single recipient, contact groups, or contacts imported from a file, as well as create SMS campaigns.

This guide explains how to configure an SMS API Gateway and start sending SMS messages through Libwana.net.


1. Open the SMS Gateway Section

Log in to your Libwana.net account.

From the left-hand menu:

Gateway → SMS → SMS API Gateway

Inside the SMS section, you will see two gateway options:

  • SMS API Gateway – Connect an SMS provider using its API.
  • Android Gateway – Use a connected Android device for SMS sending.

In this guide, we are configuring the SMS API Gateway.


2. Add a New SMS Gateway

Open SMS API Gateway and click:

+ Add Gateway

The Add SMS Gateway window will appear.

First, enter a Gateway Name that will help you identify the connection.

For example:

My Business SMS Gateway

You will also see several message delay settings.

Per Message Minimum Delay (Seconds)

Defines the minimum delay between SMS messages.

Per Message Maximum Delay (Seconds)

Defines the maximum delay between SMS messages.

Delay After Count

Defines how many messages should be sent before a sending pause is applied.

Delay After Duration (Seconds)

Defines how long sending should pause after reaching the configured message count.

Reset After Count

Defines when the sending counter should reset.

These settings are useful for controlling your sending rate. Configure them according to the limits and requirements of your SMS provider. If you do not need custom delays, you can leave the default values where appropriate.


3. Choose Your SMS API Type

Libwana.net provides two ways to connect an SMS API:

Option 1: Built-in API

Use this when your SMS provider is already supported by Libwana.net.

Option 2: Custom API

Use this when you have an SMS provider with an HTTP API that is not available as a built-in integration.

You can configure the option that matches your SMS provider. Depending on your account limits, you may also configure multiple gateways for different providers or purposes.


Option 1: Configure a Built-in SMS API

Select the Built-in API tab.

Open the Gateway Type dropdown and choose your SMS provider.

Depending on the integrations available in your account, the list may include providers such as:

  • Twilio
  • NEXMO
  • MessageBird
  • TextMagic
  • Clickatell
  • Infobip
  • SMSBroadcast
  • MIMSMS
  • AjuraSMS
  • MSG91

The exact providers available can vary.

After selecting a gateway, Libwana.net will display the configuration fields required for that provider.

For example, a provider may require information such as:

Account SID – Your SMS provider account identifier.

Auth Token – The authentication credential supplied by your SMS provider.

From Number – The phone number from which your SMS messages will be sent.

Sender ID – The sender identity used for outgoing messages, where supported.

Different providers may require different credentials. Always enter the information provided by your own SMS provider account.

Important: Never copy API credentials, tokens, phone numbers, or account IDs from screenshots, tutorials, or another user's account.

Once all required information has been entered, click Save.


Option 2: Configure a Custom SMS API

If your SMS provider is not available under Built-in API, select:

Custom API

Libwana.net provides a step-by-step configuration process consisting of:

1. API URL → 2. Headers → 3. Authorization → 4. Body → 5. Response Status

The exact configuration depends on the API documentation provided by your SMS service.


Step 1: API URL and Method

Enter the SMS sending endpoint supplied by your provider in the API URL field.

For example, your provider may give you an endpoint similar to:

https://api.example.com/send

Next, select the HTTP method required by the provider.

Depending on the API, this may be:

GET or POST

Do not select a method randomly. Use the method specified in your SMS provider's API documentation.

Query Parameters

If your SMS API expects information through query parameters, add the required keys and values.

Libwana.net provides dynamic variables including:

{{recipient}} – Recipient's phone number

{{message}} – SMS message content

For example, if your provider expects a parameter called to, you can map its value to {{recipient}}.

Click Add Query Parameter when additional parameters are required.

After completing the API URL configuration, click Next.


Step 2: Configure Headers

Add any HTTP headers required by your SMS provider.

Common APIs may require headers for content type, API keys, or other information.

Enter the exact header names and values specified in your provider's API documentation.

If your provider does not require additional headers, configure this section accordingly.

Then proceed to the next step.


Step 3: Configure Authorization

Configure the authentication method required by your SMS API.

Your provider may use an:

  • API Key
  • Access Token
  • Bearer Token
  • Username/password
  • Other authorization method

Use only the credentials supplied by your SMS provider.

API keys and authentication tokens should always be kept private.


Step 4: Configure the Request Body

If your provider uses a request body, configure it according to its API documentation.

Use Libwana.net's dynamic recipient and message variables where required:

{{recipient}}

{{message}}

These variables allow Libwana.net to automatically insert the correct phone number and SMS content whenever a message is sent.


Step 5: Configure Response Status

Finally, configure the response information that Libwana.net should use to determine whether the SMS API request was successful.

Your SMS provider's API documentation should explain the HTTP status or response value returned after a successful request.

Configure the response status accordingly and complete the gateway setup.

Click Save when finished.


4. Enable Your SMS Gateway

After saving the gateway, return to your SMS Gateways list.

Your gateway will appear with information such as:

  • Gateway Name
  • Gateway Type
  • Default
  • Status
  • Options

Make sure you enable the Status of the gateway.

If you want a particular gateway to be your primary SMS gateway, you can also enable the Default option where appropriate.

Your SMS API Gateway should be correctly configured and active before you attempt to send messages.


5. Send an SMS Through Libwana.net

After configuring your SMS gateway, go to:

Messages → SMS → Send SMS

The Send SMS page allows you to choose different types of audiences.

Single Audience

Use this option to send an SMS to an individual phone number.

Enter the recipient's phone number.

Group Audience

Use this option when you want to send SMS messages to contacts from a selected group.

Import File

Use this option when you want to import recipient data from a supported file and send messages to multiple recipients.

This makes it easier to handle larger SMS recipient lists without entering each phone number manually.


6. Select the Sending Method

Under Sending Method, select:

API Gateway

You can then select the appropriate:

API Gateway Type

and:

API Gateway

For example, if you configured a Twilio gateway, select the corresponding provider type and the gateway you created.

This tells Libwana.net which configured SMS service should be used to send your messages.


7. Send Now or Schedule Your SMS

Libwana.net also allows you to choose when your SMS should be sent.

If you want to schedule the message for later, use the Schedule At field and select the required date and time.

This can be useful for promotions, reminders, notifications, announcements, and scheduled campaigns.


8. Choose the SMS Type

Choose the appropriate SMS type:

Plain – Suitable for standard SMS text.

Unicode – Use when your message contains characters that require Unicode support, such as certain non-Latin scripts.

Be aware that SMS encoding can affect how message length and SMS segments are calculated by your provider.


9. Write Your Message

Enter your SMS content in the Message Body section.

You can also use an existing template where available.

When sending messages to contacts, Libwana.net supports personalization variables where provided by the interface. For example:

{{first_name}}

This can be used to personalize messages for individual contacts.

Before sending a bulk message, carefully review your content, audience, selected gateway, and schedule.

Then click Send.


Sending Bulk SMS with Libwana.net

Once your SMS API Gateway is active, you are not limited to sending individual messages.

You can use Libwana.net to manage SMS communication for:

Single recipients – Send directly to one phone number.

Contact groups – Send the same communication to a selected group of contacts.

Imported recipient lists – Import recipient information from a supported file and send messages at scale.

SMS campaigns – Create and manage larger campaign-based SMS communications.

Scheduled SMS – Prepare messages now and schedule them for a later date and time.


Built-in API vs. Custom API – Which Should You Use?

Use Built-in API when your SMS provider is already supported by Libwana.net. This is generally easier because Libwana.net provides the required fields for that provider.

Use Custom API when your SMS provider isn't available in the built-in list but provides an HTTP API that can be configured using its API URL, headers, authorization, request parameters/body, and response status.

In both cases, you need an active account and valid credentials from the SMS provider you want to use.


Troubleshooting SMS Gateway Setup

If your SMS messages are not being sent, check the following:

Gateway is disabled: Make sure the Status switch is enabled.

Incorrect API credentials: Verify your API key, token, Account SID, username, password, or other credentials with your SMS provider.

Incorrect sender information: Make sure your From Number or Sender ID is valid and approved by your provider where approval is required.

Custom API isn't working: Check the API URL, HTTP method, headers, authorization, query parameters, body, and expected response against your provider's API documentation.

Messages are sending too quickly: Review the delay settings and your SMS provider's rate limits.

Recipient number is rejected: Make sure phone numbers are entered in the format required by your SMS provider, including the correct country code when required.

Insufficient provider balance: Some SMS providers require prepaid credits or an active billing account. Check your provider account if requests are being rejected.


Important SMS Sending Guidelines

Use SMS messaging responsibly and send messages only where you have the appropriate permission or other lawful basis to contact recipients.

For marketing messages, follow applicable consent, opt-out, privacy, sender-registration, and telecommunications requirements for the countries in which you operate.

Your SMS provider may also impose its own restrictions, sending limits, sender verification requirements, and messaging policies.


Conclusion

Setting up an SMS API Gateway in Libwana.net allows you to connect your preferred SMS provider and manage SMS communication from one platform.

The basic process is:

Gateway → SMS → SMS API Gateway → Add Gateway → Choose Built-in API or Custom API → Configure Provider → Save → Enable Status

Once your gateway is active:

Messages → SMS → Send SMS → Choose Audience → Select API Gateway → Write Message → Send or Schedule

You can then use Libwana.net for individual SMS messages, group messaging, imported recipient lists, bulk SMS campaigns, and scheduled communications.

Whether your provider is already supported through a Built-in API or requires a Custom API configuration, Libwana.net gives you the flexibility to connect the SMS service that fits your business needs.