Custom SMS provider integration guide

Option A: Unifonic

• Unifonic App ID — the unique application ID provided by Unifonic.
• Unifonic Sender ID — the approved sender name (for example, “Signit”) registered in your Unifonic account.
• Username — account username.
• Password — account password.

Option B: T2

• Application ID — your T2 application ID.
• Sender ID — the alphanumeric sender identity approved by T2.
• Username — your T2 account username.
• Password — your T2 account password or API secret.

Option C: Msegat

• User name — your Msegat account username.
• API key — the API key generated from your Msegat dashboard.
• Sender ID — the registered sender ID for your messages.

Option D: Twilio

• Account ID — your primary Twilio account identifier.
• Auth token — the secret token used to authenticate API requests.
• Messaging Service SID — the ID of the specific messaging service configured in Twilio for this purpose.

You can find these values in the Twilio Console:

Option E: Other / custom gateway

For providers not listed, use the generic configuration:

• Gateway provider name — the name of your provider.
• Gateway API URL — the endpoint URL for sending SMS (for example, https://api.provider.com/send).
• Gateway method — select GET or POST depending on the API requirements.
• Authentication — choose “No auth,” “Basic auth,” “Bearer token,” or “API key,” then enter the credentials.
• Field mapping — map the API parameters manually:
• “Message” field — the parameter name the API expects for the message body (for example, msg or text).
• “Destination” field — the parameter name for the recipient number (for example, to or mobile).
• Additional fields — add any extra required static parameters (such as sender_id or format).