SMSWALA provider SMS API for paid users. This API can be used to integrate with your website, software, scripts to deliver messages as per your needs. Currently following actions are supported over API

Send SMS
http://122.166.100.56/api.php?user=[YourUserName]&pass=[YourPassword]&sender=[ApprovedSenderID]&mobile=[YourMobile]&message=Hello
Change Password
http://122.166.100.56/changepasswordapi.php?user=[YourUserName]&oldpassword=[YourOldPassword]&newpassword=[YourNewPassword]
Check Balance
http://122.166.100.56/balanceapi.php?user=[YourUserName]&password=[YourPassword]
Sent Report
http://122.166.100.56/sentreportapi.php?user=[YourUserName]&password=[YourPassword]&date=[yyyy-mm-dd] e.g. 2009-09-08
Schedule Message
http://122.166.100.56/schmessageapi.php?user=username&pass=pass&sender=ABC&mobile=9999999989,9999999990,9999999991&message=Hello&shtime=yyyy-MM-dd HH:mm:ss eg 2008-11-21 23:12:32

Percent-encoding in a URI

Types of URI characters

The characters allowed in a URI are either reserved or unreservedReserved characters are those characters that sometimes have special meaning, while unreserved characters have no such meaning. Using percent-encoding, characters which otherwise would not be allowed are represented using allowed characters. The sets of reserved and unreserved characters and the circumstances under which certain reserved characters have special meaning have changed slightly with each revision of specifications that govern URIs and URI schemes.

RFC 3986 section 2.2 Reserved Characters (January 2005)
! * ' ( ) ; : @ & = + $ , / ? % # [ ]
RFC 3986 section 2.3 Unreserved Characters (January 2005)
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
a b c d e f g h i j k l m n o p q r s t u v w x y z
0 1 2 3 4 5 6 7 8 9 - _ . ~

No other characters are allowed in a URI.

Percent-encoding reserved characters

When a character from the reserved set (a "reserved character") has special meaning (a "reserved purpose") in a certain context, and a URI scheme says that it is necessary to use that character for some otherpurpose, then the character must be percent-encoded. Percent-encoding a reserved character involves converting the character to its corresponding byte value in ASCII and then representing that value as a pair of hexadecimal digits. The digits, preceded by a percent sign ("%"), are then used in the URI in place of the reserved character. (For a non-ASCII character, it is typically converted to its byte sequence in UTF-8, and then each byte value is represented as above.)

The reserved character "/", for example, if used in the "path" component of a URI, has the special meaning of being a delimiter between path segments. If, according to a given URI scheme, "/" needs to be in a path segment, then the three characters "%2F" or "%2f" must be used in the segment instead of a raw "/".

Reserved characters after percent-encoding
! * " ' ( ) ; : @ & = + $ , / ? % # [ ]
%21 %2A %22 %27 %28 %29 %3B %3A %40 %26 %3D %2B %24 %2C %2F %3F %25 %23 %5B %5D

Reserved characters that have no reserved purpose in a particular context may also be percent-encoded but are not semantically different from those that are not.

In the "query" component of a URI, for example, "/" is still considered a reserved character but it normally has no reserved purpose, unless a particular URI scheme says otherwise. The character does not need to be percent-encoded when it has no reserved purpose.

URIs that differ only by whether a reserved character is percent-encoded or appears literally are normally considered not equivalent (denoting the same resource) unless it can be determined that the reserved characters in question have no reserved purpose. This determination is dependent upon the rules established for reserved characters by individual URI schemes.

Free SMS
Bulk SMS
SMS API
Email 2 SMS
Moogle
Daily Free SMS
Free Website
Trace Your IP
Mobile Tracer
Funny SMS Collection
Love Calculator
Wallpapers
Chat