Difference between revisions of "Main Page"
| Line 4: | Line 4: | ||
The Mailtrust [http://en.wikipedia.org/wiki/Api API] comprises a robust set of web services designed to allow businesses to fully integrate administrative email functions into their own applications. Based on [http://en.wikipedia.org/wiki/SOAP SOAP], functions in the API allow programs written in many different languages to perform operations such as [[AddUser()|adding mailboxes]] and changing settings. The API can also be used to provide [[LoginUserWebmail()|single sign on]] functionality in concert with other web applications. The Webmail API runs on the same robust server platform that supports our high-availability [http://www.mailtrust.com webmail] and email services. | The Mailtrust [http://en.wikipedia.org/wiki/Api API] comprises a robust set of web services designed to allow businesses to fully integrate administrative email functions into their own applications. Based on [http://en.wikipedia.org/wiki/SOAP SOAP], functions in the API allow programs written in many different languages to perform operations such as [[AddUser()|adding mailboxes]] and changing settings. The API can also be used to provide [[LoginUserWebmail()|single sign on]] functionality in concert with other web applications. The Webmail API runs on the same robust server platform that supports our high-availability [http://www.mailtrust.com webmail] and email services. | ||
| + | ---------------- | ||
| + | == API System Upgrades, March 2009 == | ||
| + | |||
| + | On March 7th the [[webmail|Webmail User API]] will be updated to use the most recent and robust systems at Mailtrust. No changes to code written by Mailtrust customers should be needed to take advantage of the update. | ||
| + | |||
| + | RISKS: After extensive testing Mailtrust has concluded that there is a risk for customers using programming libraries that send the HTTP EXPECT header with their requests. This update moves the API to a far more robust and reliable system, but the system will return errors if this header is included in a request. | ||
| + | |||
| + | An excellent discussion around turning off EXPECT headers may be found in [[http://groups.google.com/group/twitter-development-talk/browse_thread/thread/7c67ff1a2407dee7?pli=1|this discussion]] about Twitter: | ||
---------------- | ---------------- | ||
| − | |||
| − | |||
| − | |||
=== Mailtrust API === | === Mailtrust API === | ||
* [[webmail|Webmail User API]] - provides a short list of webmail user functions | * [[webmail|Webmail User API]] - provides a short list of webmail user functions | ||
| Line 39: | Line 44: | ||
* [[HTML]] (not part of the API, strictly speaking) | * [[HTML]] (not part of the API, strictly speaking) | ||
|} | |} | ||
| + | |||
| + | === Getting Started Screencast === | ||
| + | [http://www.mailtrust.com/api-wiki/screencasts/api-pings.htm Screencast] of accessing two of our SOAP API's from PHP using Ubuntu linux. | ||
=== Result Codes === | === Result Codes === | ||
Consult the [[resultcodes|Result Code Table]] for a list of result codes and their meaning. | Consult the [[resultcodes|Result Code Table]] for a list of result codes and their meaning. | ||
Revision as of 11:30, 23 February 2009
The Mailtrust API
The Mailtrust API comprises a robust set of web services designed to allow businesses to fully integrate administrative email functions into their own applications. Based on SOAP, functions in the API allow programs written in many different languages to perform operations such as adding mailboxes and changing settings. The API can also be used to provide single sign on functionality in concert with other web applications. The Webmail API runs on the same robust server platform that supports our high-availability webmail and email services.
API System Upgrades, March 2009
On March 7th the Webmail User API will be updated to use the most recent and robust systems at Mailtrust. No changes to code written by Mailtrust customers should be needed to take advantage of the update.
RISKS: After extensive testing Mailtrust has concluded that there is a risk for customers using programming libraries that send the HTTP EXPECT header with their requests. This update moves the API to a far more robust and reliable system, but the system will return errors if this header is included in a request.
An excellent discussion around turning off EXPECT headers may be found in [discussion] about Twitter:
Mailtrust API
- Webmail User API - provides a short list of webmail user functions
- Business API - provides a list of functions designed for single business/domain usage
- Reseller API - provides a complete list of functions for multiple domains and sub-accounts
- Beta API - a list of functions in public beta testing
Code Examples
|
Getting Started Screencast
Screencast of accessing two of our SOAP API's from PHP using Ubuntu linux.
Result Codes
Consult the Result Code Table for a list of result codes and their meaning.
