Explore the EWS Managed API
Updated: November 27, 2012
Learn about the Exchange Web Services (EWS) Managed API.
Applies to: Exchange Server 2007 Service Pack 1 (SP1) | Exchange Server 2010 | Exchange Server 2013 | Exchange Online | Exchange Web Services (EWS) Managed API
The EWS Managed API is a managed interface for developing client applications that use EWS. It provides unified access to Exchange server resources while using Outlook-compatible business logic. The EWS Managed API uses EWS SOAP messages to communicate with the Exchange Client Access server.
We encourage .NET Framework developers to use the EWS Managed API instead of autogenerated proxies to develop EWS clients. The EWS Managed API object model is significantly easier to use than autogenerated proxy object models.
You can use the EWS Managed API to access EWS in versions of Exchange starting with Exchange Server 2007 Service Pack 1 (SP1), including Exchange Online.
 Note |
|---|
To take advantage of the latest features in Exchange, make sure that you are using the most current version of the EWS Managed API. |
To use the EWS Managed API, you need to have the following:
The EWS Managed API, which you can download from the Microsoft Download Center. The EWS Managed API works with all versions of Exchange starting with Exchange 2007 SP1.
Note If you want to access the new features that are available in Exchange 2013, be sure to download the EWS Managed API 2.0.
A mailbox on an Exchange server that is running a version of Exchange starting with Exchange 2007 SP1, or Exchange Online. You must have the user name and credentials of the account. By default, direct EWS access is enabled for all Exchange Online plans except for the Kiosk plan.
A version of the .NET Framework starting with the .NET Framework version 3.5.
Familiarity with web services and managed programming.
The terms specified in the License information topic apply to your use of this content. Please review the terms carefully.
If you're new to programming with the EWS Managed API, or to programming Exchange client applications in general, you'll want to familiarize yourself with the technologies listed in the following table.
Technology | Description |
|---|---|
Exchange Web Services (EWS) | EWS is a set of web service operations that are used to communicate with the Exchange server. The operations enable remote client access to Exchange mailbox data. To learn more about EWS, see Create EWS and web service solutions and EWS client design overview. |
Autodiscover | Autodiscover is a web service that allows clients to discover the EWS service endpoint. It facilitates automatic client configuration. To learn more about Autodiscover, see Working with the Autodiscover service by using the EWS Managed API. |
The EWS Managed API enables your client application to access Exchange server resources. The following table lists some of the basic tasks that you can perform by using the EWS Managed API.
Task | Related topic |
|---|---|
Use the Autodiscover service to return the EWS endpoint for an email account, and get user and domain settings for the account. | Working with the Autodiscover service by using the EWS Managed API |
Manage the folders that contain your email messages, appointments, and tasks. | |
Search for folders, email messages, appointments, and tasks. | |
Create, send, forward, and reply to email messages. | |
Manage calendar appointments and meetings. | |
Besides working with the basics of email messages, appointments, and tasks, you can use the EWS Managed API to manage delegates, to synchronize a local data store with the Exchange server, to manage distribution lists, and more. The following table lists some of the additional tasks that you can perform by using the EWS Managed API.
Task | Topic |
|---|---|
Synchronize a local data store with an Exchange server. | |
Expand a distribution list into the individual email addresses in the list. | Working with distribution lists by using the EWS Managed API |
Find conversations and apply conversation actions. |
Date | Description |
|---|---|
November 27, 2012 | Removed the reference to the .NET Framework 4 requirement. |
July 16, 2012 | Initial publication |
