Sendega API documentation.pdf - GetACoder
Sendega API documentation.pdf - GetACoder
Sendega API documentation.pdf - GetACoder
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
SENDEGA <strong>API</strong> DOCUMENTATION<br />
<strong>API</strong> last updated 28.7.2008<br />
INTRODUCTION<br />
Neovada Telecom AS and its product <strong>Sendega</strong>.com is a solution and technology for micro payments and<br />
communication using SMS, MMS and WAP messaging. Neovada Telecom AS act as a transparent, white‐label<br />
Content Acquirer and Transaction Router between Operators and Content Providers. Content Providers are<br />
provided with an easily implemented interface to connect to <strong>Sendega</strong>.com, which handles integration to the<br />
Operators.<br />
This document provides a description of how to integrate the Content Provider’s services for sending and<br />
receiving SMS, MMS and WAP messages trough the <strong>Sendega</strong>.com system. The document is intended for<br />
technical architects and designers of the Content Provider’s services.<br />
OVERVIEW<br />
<strong>Sendega</strong> <strong>API</strong> consists of a set of methods for sending and receiving SMS, MMS and WAP messages. All<br />
responses in HTTP are answered with XML. Customer ID (CID) and password must always be used when using<br />
the methods.<br />
SECURITY<br />
All IP addresses for servers that will communicate via the <strong>API</strong> should be registered with us to prevent<br />
unauthorised persons sending SMS messages from your account. IP addresses can be registered on our<br />
customer pages at <strong>Sendega</strong>.com<br />
FORMATS AND STANDARDS<br />
All values are sent/received must be as described in this document. The date format is ISO‐8601. YYYY‐MM‐DD<br />
HH:MM Return values comply with xml version 1.0 and use ISO‐8859‐1 encoding. All return xml are guaranteed<br />
“well formed”, and follow the template settings in this <strong>API</strong> for each individual method.<br />
Enquiries to <strong>Sendega</strong>.com system can either be POST or GET. We recommend POST for methods where a long<br />
message, or many telephone numbers, etc, are sent, as GET has a limitation in the length of the address string.<br />
All communication takes place via HTTP POST/GET. We support both standard http, and https for encrypted<br />
connection.<br />
http://api.sendega.com<br />
https://api.sendega.com<br />
4