Custom SMS/Text Providers

LoginRadius allows developers to configure and integrate any third-party SMS/Text provider. This functionality enables text-based communications such as One-Time Passwords (OTP) for multi-factor authentication, phone number verification, and transactional messages.

By supporting various providers, developers can align their SMS strategy with regional regulations, delivery speed, or cost requirements. The integration process remains consistent whether you use globally recognized services like Twilio, localized providers like TextLocal, or other platforms like MessageBird. You can customize authentication types, headers, body formats, and delivery endpoints to match your provider's API specifications, giving you full control over how messages are constructed and sent.

Key Features

The custom SMS/Text provider configuration offers flexibility and control, enabling seamless integration with various third-party services. Below are the key capabilities that support scalable and secure text communication through LoginRadius.

• Integrate any third-party SMS/Text provider of your choice.
• Support multiple authentication methods: Basic Auth, Bearer Token, or No Authentication.
• Customize request headers, body formats, and query parameters.
• Placeholder support for dynamic message generation.
• Seamless use within LoginRadius workflows such as OTP and phone-based authentication.

Use Cases

These examples highlight practical scenarios where integrating a custom SMS/Text provider can enhance authentication workflows, improve message delivery, and support region-specific or platform-specific requirements.

• Send OTPs via a regional SMS provider to improve delivery rates.
• Use an internal gateway for enterprise-level text communications.
• Enable SMS communication through platforms like WhatsApp or Line via custom integration.
• Leverage analytics by including custom headers or query parameters for reporting.

Configure a Custom SMS/Text Provider

Set up your preferred third-party SMS service with LoginRadius by following the steps below in the Admin Console.

1. Navigate to Admin Console > Branding > Email-SMS-Provider.

2. Select Custom Text/SMS Provider from the provider dropdown menu.

Configuration Fields

You'll need to fill in specific fields to complete the integration of your custom provider.

Delivery Provider URL

This API endpoint URL is used to send SMS requests via your provider.

• Enter the endpoint URL provided by your SMS provider.

• This URL varies by provider. Refer to the provider's documentation or use a sample cURL request to identify it.

Authentication Type

You can choose how your request is authenticated when sent to the provider. Options include Basic Authentication, Bearer Token, or No Authentication.

Basic Authentication

When Basic Authentication is selected, you must enter a Username and Password—typically your provider’s SID and Auth Token. Some providers may use an API key or alternative credentials. You must also specify the appropriate HTTP method (e.g., GET, POST, or PUT) as your provider’s API requires.

• Requires a Username and Password (e.g., SID and Auth Token).

• Specify the HTTP Method (GET, POST, or PUT).

Example cURL Request (Basic Auth):

curl 'https://api.provider.com/send' -X POST \
--data-urlencode 'To=[Receiver Phone]' \
--data-urlencode 'From=[Sender Phone]' \
--data-urlencode 'Body=[Message]' \
-u [Username]:[Password]

Bearer

When Bearer is selected, you must provide a valid Bearer Token in the authorization header and specify the required HTTP method (e.g., GET, POST, or PUT) based on your provider’s API.

• Requires a Bearer Token.
• Specify the HTTP Method (GET, POST, or PUT).

Example cURL Request (Bearer Token):

curl --location 'https://api.provider.com/send' \
--header 'Authorization: Bearer [Token]'

No Authentication

When No Authentication is selected, no credentials are required—such as username, password, or bearer token. However, you still need to specify the appropriate HTTP method as defined by your provider’s API.

• No credentials are required.
• You still need to define the HTTP Method.

Example cURL Request (No Authentication):

curl --location --request PUT 'https://api.provider.com/send?apikey=[API_KEY]&numbers=[Phone]&message=Hello'

Body Format

Define the message content format and placeholders for sending SMS.

• Choose between JSON or x-www-form-urlencoded formats.
• Enter the sender's phone number and message body.
• You can use placeholder tags such as:

"body": "#template#",
"to": "#receiver#"

Headers (Optional)

Include any headers your provider requires, such as custom tracking or authorization.

• Add custom header fields as required by the provider.
• Use the "Add Row" button to input additional headers.

This is useful for analytics purposes or to meet specific provider requirements.

Query Parameters (Optional)

Use query parameters to append extra data to your request URL.

• Provide key-value pairs as needed.
• Add additional parameters using the "Add Row" button.

Note: These values are optional and depend on your selected SMS provider’s requirements.

Once all required fields are filled:

• Save your settings.
• Test the integration to confirm successful message delivery.

Feel free to contact the LoginRadius Support team if you need assistance.

Related Resources

• SMS Communication and Configuration
• Configuring Twilio account with LoginRadius
• Branding and Customisation
• Email Communications and Configuration
• SMTP Providers