UGSMS Integration (Allios)

Send transactional alerts, reminders and 2FA SMS from Allios using the UGSMS gateway. This page summarises integration steps, sample requests and best practices.

Get Started - UGSMS

What Allios Uses UGSMS For

Send OTPs for two-factor authentication.
Send transactional alerts (e.g. payment confirmations, appointment reminders).
Save delivery reports and message status for compliance.
Manage opt-in/opt-out preferences for users.

Use-cases

Transactional alerts for deposits, withdrawals, payments.
Appointment & booking reminders for clinics and hotels.
Announcements to parents, students or members.
Delivery of 2FA/verification codes.

All of the above are supported in the Allios design—these examples map directly to typical gateway operations (send, check status, DLRs).

Permissions & compliance

Only send SMS to users who have provided explicit consent. Respect opt-in/opt-out rules (offer a clear STOP/STOPALL reply flow). Track and store Delivery Reports (DLRs) for operational accountability but avoid sharing content with third parties without consent.

Tip: keep a "consent timestamp" and store the message template version to prove consent to regulators or carriers.

API Quickstart

Most Ugandan SMS gateways use a RESTful HTTP interface: We send POST with (JSON or form) payload to an endpoint such as /v1/sms/send, authenticate with credentials (API key, or username/password), then receive a message status.

Please Note

All Allios makes API requests with the following details

API_BASE_URL — replace with your provider base (e.g. https://api.ugsms.example).
USERNAME / PASSWORD — your UGSMS credentials.

Endpoints

POST /v1/sms/send — Send one or bulk messages
GET /v1/sms/status
GET /v1/sms/balance

This API does not provide all endpoints of our expectations; consult provider documentation for full details.

Security & Data Handling

We Use HTTPS for all API calls to avoid interception of content or credentials.
If provider supports API keys or token-based auth, prefer it over username/password for better rotation and scoping.
We Store phone numbers, message and other details inside tenant-specific databases. Retain only what you need for compliance and troubleshooting.
Respect opt-out: We implement automatic suppression lists when users reply "STOP" and propagate that across all message flows.
Please Read Our guidelines regarding the storage of credentials on the opt-in page on your dashboard.

Suggested User Consent Wording

Please note that we dont collect consent from your respective clients for sms notifications. Any messages sent are considered transactional and necessary for the service. and you are liable for use of such details. For more details read our Privacy policy and for any guidance reach out to our DPO

Store a record of the consent when the phone is added to the tenant profile

References & helpful links

Replace the placeholder links above with the actual provider dashboard & docs you receive from UGSMS when you create an account.