Difference between revisions of "Main Page"
m |
m (changed Mailtrust to Rackspace Email) |
||
| Line 1: | Line 1: | ||
__NOTOC__ | __NOTOC__ | ||
| − | == The | + | == The Rackspace Email API == |
| − | The | + | The Rackspace Email [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.rackspace.com/email_hosting webmail] and email services. |
---------------- | ---------------- | ||
== API System Upgrades, March 2009 == | == 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 | + | On March 7th the [[webmail|Webmail User API]] will be updated to use the most recent and robust systems at Rackspace Email. No changes to code written by Rackspace Email customers should be needed to take advantage of the update. If desired, code may be updated to use the latest URI found in the [[webmail|Webmail User API]] documentation, though the old URI will be automatically redirected to the new URI by Rackspace Email on March 7th. |
| − | RISKS: After extensive testing | + | RISKS: After extensive testing Rackspace Email 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 much more robust and scalable system, but the system will return errors if this header is included in a request. |
An excellent discussion around turning off EXPECT headers for .NET and PHP may be found in this [http://groups.google.com/group/twitter-development-talk/browse_thread/thread/7c67ff1a2407dee7?pli=1 thread] about Twitter. | An excellent discussion around turning off EXPECT headers for .NET and PHP may be found in this [http://groups.google.com/group/twitter-development-talk/browse_thread/thread/7c67ff1a2407dee7?pli=1 thread] about Twitter. | ||
---------------- | ---------------- | ||
| − | === | + | === Rackspace Email 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 | ||
Revision as of 14:27, 27 May 2009
The Rackspace Email API
The Rackspace Email 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 Rackspace Email. No changes to code written by Rackspace Email customers should be needed to take advantage of the update. If desired, code may be updated to use the latest URI found in the Webmail User API documentation, though the old URI will be automatically redirected to the new URI by Rackspace Email on March 7th.
RISKS: After extensive testing Rackspace Email 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 much more robust and scalable system, but the system will return errors if this header is included in a request.
An excellent discussion around turning off EXPECT headers for .NET and PHP may be found in this thread about Twitter.
Rackspace Email 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.
