The main SOAP interface uses a SOAP Header to carry the user and account information. In some development/runtime environments support for SOAP headers is either complex to implement (e.g. MS SOAP Toolkit) or not provided for (e.g. ColdFusion). Some environments also do not have support for enumerated types.
Due to these limitations, we provide this alternative service implementation that does not require SOAP Headers or use enumerated types.
The SOAP XML SMS API - No Headers API provides functionality through the following services:
Sending
| Service |
Overview |
Links |
| SendServiceNoHeader |
Methods to send SMS messages individually and in batches |
URI,WSDL |
| SendContentServiceNoHeader |
Methods to send SMS messages for delivering content, eg WAP Push, individually and in batches |
URI,WSDL |
| ScheduledSendServiceNoHeader |
Submits a message to Esendex that is scheduled to be sent at a later date/time |
URI,WSDL |
Notes
The service aliasing feature within the SendMessageFull and SendMessageMultipleRecipientsFull methods of SendService is not available with Evaluation or Premium accounts. When using these methods, you must set the Originator parameter to your account reference or you will receive an error when attempting to send a message.
Receiving
| Service |
Overview |
Links |
| InboxServiceNoHeader |
Manage incoming messages queued in the account inbox |
URI,WSDL |
Other
| Service |
Overview |
Links |
| AccountServiceNoHeader |
Account management functionality |
URI,WSDL |
| ContactServiceNoHeader |
Methods to manage contacts and contact groups for an account |
URI,WSDL |
| SubscriptionServiceNoHeader |
Subscription management functionality |
URI,WSDL |