SmsService
The following operations are supported. For a formal definition, please review the Service Description.
-
AddContact
Add a Contact to the database. Returns empty Guid if there is a problem. -
Copyright
Get Copyright String. ©redware research limited 2007. -
DeleteContact
Delete a Contact. -
GetBalance
Get the balance (number of SMS credits) remaining for this session token. -1.00 returned for an invalid token. -
GetContact
Get Contact details using Guid. -
GetContactDataSet
Get Contact details using Guid. -
GetContactXML
Get Contact details using Guid. -
GetContacts
Get Contacts details. Search term will look at beginning of number, name, surname, firstname and company fields. Use % as wildcard. -
GetContactsDataSet
Get Contacts details. Search term will look at beginning of number, name, surname, firstname and company fields. Use % as wildcard. -
GetContactsXML
Get Contact details. -
GetSmsMessageHistoryDataSet
Get message history. -
GetSmsMessageHistoryXML
Get message history. -
GetUser
Get user object. -
GetUserDetailsDataSet
Get user details. -
GetUserDetailsXML
Get user details. -
GetUserServices
Get services for current user. -
Login
Login to the SMS Service and returns a token string for subsequent use. Token may time out. -
RegisterMobile
Register Outgoing Mobile. Sends a pin to register outgoing number for this user. Call method once without PIN to send message then again with the PIN to register -
SendSms
Sends an SMS message. Number and Message strings required but Reply can be empty and defaults to user settings (or redware). Returns empty Guid if there is a problem. -
SendSmsFlash
Sends an SMS Flash message. Number and Message strings required but Reply can be empty and defaults to user settings (or redware). Returns empty Guid if there is a problem. -
SendSmsScheduled
Sends a scheduled SMS message. -
UpdateContact
Update Contact. Watch out for long strings causing problems. -
UpdateService
Update Service. -
UpdateSms
Update SMS. Change the completed date and the status. -
UpdateUser
Update user. -
UpdateUserDetails
Update user details. Watch out for long strings causing problems.
This web service is using http://tempuri.org/ as its default namespace.
Recommendation: Change the default namespace before the XML Web service is made public.
Each XML Web service needs a unique namespace in order for client applications to distinguish it from other services on the Web. http://tempuri.org/ is available for XML Web services that are under development, but published XML Web services should use a more permanent namespace.
Your XML Web service should be identified by a namespace that you control. For example, you can use your company's Internet domain name as part of the namespace. Although many XML Web service namespaces look like URLs, they need not point to actual resources on the Web. (XML Web service namespaces are URIs.)
For XML Web services creating using ASP.NET, the default namespace can be changed using the WebService attribute's Namespace property. The WebService attribute is an attribute applied to the class that contains the XML Web service methods. Below is a code example that sets the namespace to "http://microsoft.com/webservices/":
C#
[WebService(Namespace="http://microsoft.com/webservices/")] public class MyWebService { // implementation }
Visual Basic
<WebService(Namespace:="http://microsoft.com/webservices/")> Public Class MyWebService ' implementation End Class
C++
[WebService(Namespace="http://microsoft.com/webservices/")] public ref class MyWebService { // implementation };
For more details on XML namespaces, see the W3C recommendation on Namespaces in XML.
For more details on WSDL, see the WSDL Specification.
For more details on URIs, see RFC 2396.