Web services in Exchange
Updated: December 17, 2013
Discover the web services that are available in Exchange Server, Exchange Online, and Exchange Online as part of Office 365.
Applies to: Exchange 2013 | Exchange Online | Office 365 | EWS Managed API
You can use Exchange Web Services (EWS) and other web services in Exchange to create solutions that enable your users to access Exchange mailbox data from services, websites, desktop computers, and mobile devices. This article describes the web services that are available in Exchange.
The terms specified in License information apply to your use of this content. Please review the terms carefully.
EWS is a web service API that you can use to communicate with Exchange. EWS provides Exchange mailbox user’s data to any website, device, or computer that can connect to the Internet. EWS was introduced in Exchange Server 2007 and is available for Exchange Server, Exchange Online, and Exchange Online as part of Office 365. Learn more about EWS by digging into the web services content, reading about the EWS operations, and by using the EWS reference when you start developing your solutions.
The SOAP Autodiscover service was introduced in Exchange 2010. If you are targeting a version of Exchange starting with Exchange 2010, including Exchange Online, we recommend that you use the SOAP Autodiscover service, rather than the POX Autodiscover service, to get client configuration data from Exchange. Like the POX Autodiscover service, the SOAP Autodiscover service provides configuration information, such as the EWS URL, but it allows for more granular control over the requested settings. The SOAP Autodiscover service also provides additional information about the federated status of an organization. For more information about the SOAP Autodiscover service, see Autodiscover for Exchange.
The "plain old XML" (POX) Autodiscover service enables applications to automatically configure user settings. You can use the Autodiscover service to determine client settings based only on a user email address. The end result of using the POX Autodiscover service is that a client can automatically get the EWS service URL.
You can use the POX Autodiscover service to configure client applications that target versions of Exchange starting with Exchange 2007, including Exchange Online. Note that the POX Autodiscover service does not enable you to specify which settings are returned in a response. We recommend that clients that target versions of Exchange starting with Exchange 2010, including Exchange Online, use the SOAP Autodiscover service, because it provides for more granular control over requested settings. For more information about the POX Autodiscover service, see Autodiscover for Exchange. For inspirational music about Autodiscover, download this song.
The Unified Messaging (UM) web service was introduced in Exchange 2007. It provides a set of operations that enable a client to access UM functionality such as initiating and managing phone calls that play mailbox items (including voice mail messages) on telephony devices, UM PIN reset, enabling missed call notifications, turning on voice Out of Office (OOF) greetings, and getting UM settings. In versions of Exchange starting with Exchange 2010, including Exchange Online, EWS provides some UM functionality. For more information, see Unified Messaging on TechNet.
The EWS Managed API is the preferred client-side object model for .NET Framework developers who want to connect to any of the following web services:
SOAP EWS service
POX Autodiscover service
SOAP Autodiscover service
Create EWS and web service solutions for Exchange – Contains overviews, code examples, and step-by-step information about the web services that are included in Exchange.
Web services reference for Exchange 2013 – Contains reference information for the EWS, Autodiscover, and Unified Messaging web services.
EWS wsdl.exe autogenerated reference for Exchange 2013 – Contains the EWS auto-generated proxy object reference set.
The autogenerated proxy reference is deemphasized. We recommend that you use the EWS Managed API instead of an autogenerated proxy to develop EWS solutions.