Export (0) Print
Expand All
Expand Minimize
This topic has not yet been rated - Rate this topic

GetAppManifests operation

Exchange Server 2013

Published: July 16, 2012

Find information about the GetAppManifests EWS operation.

Applies to:  Exchange Online | Exchange Server 2013 | Office 365 

The GetAppManifests operation retrieves app manifests.

This operation was introduced in Exchange Server 2013.

The GetAppManifests operation does not take any arguments to request the app manifests for a mailbox. The response will contain base64-encoded XML manifest files for each app that is installed in a mailbox.

GetAppManifests operation SOAP headers

The GetAppManifests operation can use the SOAP headers that are listed in the following table.

Header name

Element

Description

RequestVersion

RequestServerVersion

Identifies the schema version for the operation request. This header is applicable to a request.

ServerVersion

ServerVersionInfo

Identifies the version of the server that responded to the request. This header is applicable to a response.

The following example of a GetAppManifests operation request shows how to get the app manifests for a mailbox.

<?xml version="1.0" encoding="UTF-8"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
               xmlns:t="http://schemas.microsoft.com/exchange/services/2006/types"
               xmlns:m="http://schemas.microsoft.com/exchange/services/2006/messages">
   <soap:Header>
      <t:RequestServerVersion Version="Exchange2013" />
      <t:MailboxCulture>en-US</t:MailboxCulture>
      <t:TimeZoneContext>
         <t:TimeZoneDefinition Id="GMT Standard Time"/>
      </t:TimeZoneContext>
   </soap:Header>
   <soap:Body >
      <m:GetAppManifests/>
   </soap:Body>
</soap:Envelope>

The request SOAP body contains the following element:

The following example shows a successful response to a GetAppManifests operation request to get the app manifests for a mailbox.

Note Note

All base64 app manifests have been arbitrarily truncated to preserve readability.

<?xml version="1.0" encoding="utf-8"?>
<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">
   <s:Header>
      <h:ServerVersionInfo MajorVersion="15" 
                           MinorVersion="0" 
                           MajorBuildNumber="556" 
                           MinorBuildNumber="14" 
                           Version="Exchange2013" 
                           xmlns:h="http://schemas.microsoft.com/exchange/services/2006/types" 
                           xmlns="http://schemas.microsoft.com/exchange/services/2006/types" 
                           xmlns:xsd="http://www.w3.org/2001/XMLSchema" 
                           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
   </s:Header>
   <s:Body xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
           xmlns:xsd="http://www.w3.org/2001/XMLSchema">
      <GetAppManifestsResponse ResponseClass="Success" 
                               xmlns="http://schemas.microsoft.com/exchange/services/2006/messages">
         <ResponseCode>NoError</ResponseCode>
         <m:Manifests xmlns:m="http://schemas.microsoft.com/exchange/services/2006/messages">    
<m:Manifest>lQXBwPg==</m:Manifest>
<m:Manifest>QXBwPg==</m:Manifest>
         </m:Manifests>
      </GetAppManifestsResponse>
   </s:Body>
</s:Envelope>

The response SOAP body contains the following elements:

Because the GetAppManifests operation does not take any arguments, you cannot send incorrect arguments to the service. For error codes that are generic to EWS and specific to this operation, see ResponseCode.

Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft. All rights reserved.