Netcore SMS API Overview

• This document provides a description of the Netcore Bulk push API usage for end-users .
• This document also describes the API for collecting delivery reports as well.

PE-TM Chain Binding on DLT as per TRAI Mandate for SMS

As of December 11, 2024, all Principal Entities (PEs) must comply with the TRAI mandate to disclose the entire chain through which SMS communications are routed, including all Registered Telemarketers (RTMs) involved. Failure to meet this requirement may result in complete SMS delivery failures starting from this date.

We support Twilio gateway for SMS integration.

Mobile number guidelines in API usage

• For GSM & CDMA messaging, the Receiver Phone Number must start with country code - e.g. 91 in case of an Indian number.
• No leading ‗0‘ or ‗+‘ are allowed—e.g., the number, 99860XXXXX, should be specified as 9199860XXXXX. This means the number should always be prefixed by 91 with no leading ‗+‘ or 0‘s.
• For sending message internationally the mobile number should be prefixed with ‘00’ the appropriate country code, followed by the mobile number. For all local Indian numbers, the mobile number must be 12-digit long. No special character like "-", "(",")" or anything similar is allowed in the phone number, e.g., 91-98123XXXXX is disallowed.

Choice between IP address & mobile number authentication

To be able to use our APIs the enterprise needs to choose between 2 access mechanisms.

White listing client public IP addresses

• The series :- 10.0.0.0 through 10.255.255.255 172.16.0.0 through 172.31.255.255 192.168.0.0 through 192.168.255.255 are internal/private IP series and cannot be given for white listing.

Mobile number & password authentication.

• You need supply a Valid mobile number which will be registered for the API account.

• The account details with the password will be shared with you by customer support team.

SMS Header and Footer

• Messages may need to be sent out with a fixed header and/ or footer in some cases. For instance, an Enterprise would want all messages to be signed-off with their name or all offers with Terms of Service/ Use. SMS Header and footer settings can be used for help in this regard.
• If the header is set, all messages sent will be prefixed with the header content. Similarly, if the footer is set, all messages sent out via the API will end with the footer content.
• For e.g : We have set the header of the message as ‗Dear Customer,‘ and the footer of the message as ‗Happy Shopping!‘. If the message text: ‗We have come up with a special offer for all our customer with a flat discount of 50% and more T&C apply. Visit your nearest store.‘ is specified in the API call, the message to the end recipient will be sent out as: ‗Dear Customer, We have come up with a special offer for all our customer with a flat discount of 50% and more T&C apply. Visit your nearest store. Happy Shopping!‘. The Header and Footer can be set from the BizBond dashboard from Keyword -> Message Customization.

Acronyms and Abbreviations

The acronyms and abbreviations expanded in Table 1-2 are fundamental to the information in this document.

Table 1-2: Acronyms and abbreviations used in this document