This single endpoint (/bulksms/personalizedbulksms) covers two related use cases, shown separately below. Both use the same endpoint, parameters, and authentication — the only difference is which parameters you use in the request.

Use case 1: Multilingual API — send regional-language content directly

Send message content in any regional language directly, with no need to convert it to UCS2 hexadecimal first. Use this when your message does not contain a URL that needs shortening.

Sample request URL:

https://sms-eu.rmlconnect.net:8443/bulksms/personalizedbulksms?username=your_username&password=your_password&source=TESTSM&destination=91XXXXXXXXXX&type=0&message=Namaste%20World&tagname=campaign1

Use case 2: Multilingual Acculync API — regional-language content + URL shortening

Use this when your message contains a URL that you want the platform to automatically shorten before delivery. Set toshorten=Y and pass the URL(s) to shorten in tobeshorten (URL-encoded, up to four, separated by ||-||). Regional-language content is still sent directly here too — no UCS2 conversion needed.

Sample request URL:

https://sms-eu.rmlconnect.net:8443/bulksms/personalizedbulksms?username=your_username&password=your_password&source=TESTSM&destination=91XXXXXXXXXX&type=0&message=Namaste%20World%20https%3A%2F%2Fexample.com&tagname=campaign1&toshorten=Y&tobeshorten=https%3A%2F%2Fexample.com&udf1=txn123&isCL=1

In short: if your message is plain regional-language text, you're using this as the Multilingual API. If your message also includes a URL you want shortened, you're using the same endpoint as the Multilingual Acculync API. Either way, this is distinct from the Acculync API below, where regional-language content must be UCS2-encoded before submission.