EWS XML elements in Exchange 2013
Published: July 16, 2012
Find reference information for the EWS XML elements in Exchange.
Applies to: Exchange 2013 | Exchange Online | Exchange Server 2007 | Exchange Server 2010
Exchange Web Services (EWS) is a SOAP-based web service, which means that the request and response messages that are sent between the client and server are comprised of XML elements. The documentation in this section is based on the XML instances that are sent between the client and server. The XML instances are defined in the WSDL and schema files that are located in the virtual directory that hosts EWS. If you are an authenticated user, you can browse to the WSDL and schema files by using the following URLs, where <yourclientaccessserver> is the name of your Client Access server:
http://<yourclientaccessserver>.com/ews/services.wsdl — The location of the WSDL file.
http://<yourclientaccessserver>.com/ews/messages.xsd — The location of the messages schema.
http://<yourclientaccessserver>.com/ews/types.xsd — The location of the types schema.
The schema files that describe the EWS XML elements provide a general roadmap of the XML structure that is possible for request-response message interactions. The actual XML structure that is sent between client and server varies according to the operation that is called, the information requested, and the server-side settings.
The EWS WSDL file, services.wsdl, does not fully conform to the WSDL standard because it does not include a WSDL service definition. This is because EWS is not designed to be hosted on a computer that has a predefined address. You can use the Autodiscover service to get the EWS endpoint address. Some client-side object model generators parse the WSDL and can encounter an error condition because the WSDL file does not contain a WSDL service definition. If your object model generator encounters an error, you can insert a placeholder WSDL service definition.
If you are using the .NET Framework to develop your application, we recommend that you use the EWS Managed API, rather than an object model generator. The EWS Managed API provides an easy-to-use object model to handle the serialization and deserialization of the EWS XML. For more information, see EWS Managed API. You can download the API from the Microsoft Download Center. If you are using Java to develop your application, you can use the EWS Java API, which is a Java port of the EWS Managed API. You can download the EWS Java API from MSDN.
The messages.xsd schema file contains the element definitions for the top-level elements in the SOAP body. With the exception of the error response codes, most of the definitions in messages.xsd are specific to an operation. The types.xsd schema contains the definitions for the SOAP headers and all the common definitions that are shared across operations.