Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Find information about the InstallApp EWS operation.
The InstallApp operation installs a mail app for Outlook in a mailbox.
This operation was introduced in Exchange Server 2013.
Using the InstallApp operation
The InstallApp operation takes a single argument that identifies a mail app to install. The argument contains the base64-encoded manifest for a mail app.
InstallApp operation SOAP headers
The InstallApp 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. |
InstallApp operation request example: Install a mail app in a mailbox
The following example of an InstallApp operation request shows how to install a mail app for Outlook. The app manifest can be found by using the GetAppManifests operation.
Note
The base64-encoded app manifest has been arbitrarily truncated to preserve readability and does not represent a valid manifest.
<?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" />
</soap:Header>
<soap:Body >
<m:InstallApp>
<m:Manifest>TUwiIC8+CiAgPC9SdWxlPgo8L09mZmljZUFwcD4=</m:Manifest>
</m:InstallApp>
</soap:Body>
</soap:Envelope>
The request SOAP body contains the following elements:
Successful InstallApp operation response
The following example shows a successful response to an InstallApp operation request to install a mail app.
<?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">
<InstallAppResponse ResponseClass="Success"
xmlns="http://schemas.microsoft.com/exchange/services/2006/messages">
<ResponseCode>NoError</ResponseCode>
</InstallAppResponse>
</s:Body>
</s:Envelope>
The response SOAP body contains the following elements:
InstallApp operation error response
The following example shows an error response to an InstallApp operation request. This is a response to a request that contains an invalid manifest.
<?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">
<InstallAppResponse ResponseClass="Error"
xmlns="http://schemas.microsoft.com/exchange/services/2006/messages">
<MessageText>This app can't be installed. Missing OfficeApp element.</MessageText>
<ResponseCode>ErrorInternalServerError</ResponseCode>
<DescriptiveLinkKey>0</DescriptiveLinkKey>
</InstallAppResponse>
</s:Body>
</s:Envelope>
The error response SOAP body contains the following elements: