Sending WAP push messages
Base URL
Nvia supports sending of WAP push messages over a simplified HTTP mechanism. The base URL to which partners must request the sending of an SMS is:
Parameters
To send the SMS, partners must use the following parameters in the base URL:
User
User Identifier within the Nvia Platform (contact e-mail).
Yes
Password
User’s password. For security reasons, each user must use their password for each HTTP petition.
Yes
to
Phone number to where the SMS will be delivered. The number must be in international format and URL encoded (for instance: +1 222 333 444 will be URL encoded as %2B1222333444).
Yes
text
Content of the message which will be delivered to the handset. The content must be URL encoded.
Yes
URL
URL sent in the WAP push.
Yes
Confirmation
Used if the user desires a delivery report with the status of the SMS. Can be set to true or false.
No
senderId
Sender of the message. Limited to 11 characters.
No
validityPeriod
Validity period can be set in a relative and an absolute format. Please check the section dedicated to datetime formats for more information. Please note that not all operators support validity period. Contact your account manager for more information.
No
scheduledDeliveryTime
Scheduled delivery time can be sent in a relative and an absolute format. Please check the section dedicated to datetime formats for more information. Please note that not all operators support validity period. Contact your account manager for more information.
No
Outputs
If the user’s petition is correct, Nvia’s SMSC will answer in plain text the following:
is the identifier of the message in the system. This value can be used by the sender to match the SMS with the delivery report.
If the user’s petition is incorrect, the SMSC will answer with a text and an error code as follows:
is the numeric identifier of the error. Details regarding the error codes can be found in the appropriate sector in this document.