NEnetcorecloud
Send Message

Send SMS (POST)

The Send SMS (POST) endpoint allows you to send single or bulk SMS messages using a form-urlencoded request body. This method is recommended for production use as it provides:

  • Better security (no credentials in URL)
  • Support for larger payloads
  • Improved reliability for bulk messaging

The API supports DLT/TRAI compliance, scheduled delivery, bulk messaging, and message tracking.

The API also supports advanced optional parameters such as: tokenkey, hexflag, mtype, url, udh, dlt_template_type, jobname, jobid, ssl, ssliv, aesKey, account, DeptID, AppID, short, itemtags, enterpriseid, hibernate, checkndnc, response_type.

post/SingleMsgApi

Request

  • Base URL
    https://smsapi.netcorecloud.net/BulkSms
  • URL
    https://smsapi.netcorecloud.net/BulkSms/SingleMsgApi
  • Auth
    none required

Request body application/x-www-form-urlencoded

feedidstring required

Unique account/feed ID used to identify the sender account.

usernamestring

Username for authenticating the API request.

passwordstring

Password associated with the username for authentication.

Tostring required

Comma-separated list of recipient mobile numbers.

Textstring required

SMS message content to be sent to recipients.

senderidstring

Sender ID displayed as the message sender on the recipient’s device.

templateidstring

DLT-approved template ID required for regulatory compliance.

entityidstring

DLT entity ID representing the registered sender/business.

async'0' | '1'

Defines processing mode (0 = synchronous, 1 = asynchronous).

timestring

Scheduled delivery time in yyyymmddhhmm format.

tzstring

Timezone for scheduled message delivery (e.g., GMT+05:30).

msgidstring

Client-defined unique message ID for tracking and duplicate detection.

Example request

{
  "feedid": "392095",
  "username": "your_username",
  "password": "your_password",
  "To": "9870524533,9956808517",
  "Text": "Your OTP is 123456.",
  "senderid": "TXTLCL",
  "templateid": "1107168518658504806",
  "entityid": "1201159871062710104"
}

Response

A successful request returns an HTTP 200 response, indicating that the SMS request has been accepted and processed by the system.

Changes

No recorded changes to this operation across all 1 revision of this API.