Message Submission with Token

Notif+ Platform - Message Submission with Token

Submit an SMS using a pre-generated authentication token instead of passing credentials with every request. Obtain the token from the Token Generation API.

Exemple usage

https://<servername>:<port>/bulksms/bulksubmit?token=-xxxxxxx&message=xxxxx&source=xxxxxx&destination=21377XXXXXXX&type=0&dlr=1

Paramètre

Field	Type	Description
username	string	Username of the user.
password	string	Password of the user.
type	string	It indicates the type of message. Values for "type" include: 0: Plain text (GSM 3.38 Character encoding) 1: Flash (GSM 3.38 Character encoding) 2: Unicode 3: Reserved 5: Plain text (ISO-8859-1 Character encoding) 6: Unicode Flash 7: Flash (ISO-8859-1 Character encoding)
dlr	string	Indicates whether the client wants delivery report for this message. The values for "dlr" include: 0: No delivery report required 1: Delivery report required
destination	string	Mobile number to which the message is to be sent (may or may not include a plus [+] sign). Multiple mobile numbers need to be separated by a comma (,) (the comma should be URL encoded).
source	string	The source address that should appear in the message. - Max Length of 18 if numeric. - Max Length of 11 if alphanumeric. To prefix the plus sign (+) to the sender’s address when the message is displayed on their mobile phone, please prefix the plus sign to your sender’s address while submitting the message. Note: You need to URL encode the plus sign. The SMSC may enforce additional restrictions on this field.
message	string	The message to be sent. It can be used for 'long' messages, that is, messages longer than 160 characters for plain text, 140 for flash, and 280 for Unicode. For concatenated (long) messages every 153 characters are counted as one message for plain text and 268 characters for Unicode. The system uses the rest of the characters for packing extra information for reassembling the message on the mobile phone.

Success Code

Field	Description
1701	Success. Message submitted successfully. Response will be in below format : 1701 "CELL_NO" "MESSAGE_ID" You can then use the message ID later to map the delivery report to the message.

Success response

1701|Destination:Messageid

Error Codes

Nom	Description
1702	Invalid URL. This means that one of the parameters was not provided or left blank.
1703	Invalid value in username or password field.
1704	Invalid message type.
1705	Invalid message.
1706	Invalid destination.
1707	Invalid source (Sender ID).
1708	Invalid dlr value.
1709	User validation has failed.
1710	Internal error.
1715	Response timeout.