Server and File Management Web Apis Protocol
Total Page:16
File Type:pdf, Size:1020Kb

[MS-SFMWA]: Server and File Management Web APIs Protocol
Intellectual Property Rights Notice for Open Specifications Documentation § Technical Documentation. Microsoft publishes Open Specifications documentation (“this documentation”) for protocols, file formats, data portability, computer languages, and standards support. Additionally, overview documents cover inter-protocol relationships and interactions. § Copyrights. This documentation is covered by Microsoft copyrights. Regardless of any other terms that are contained in the terms of use for the Microsoft website that hosts this documentation, you can make copies of it in order to develop implementations of the technologies that are described in this documentation and can distribute portions of it in your implementations that use these technologies or in your documentation as necessary to properly document the implementation. You can also distribute in your implementation, with or without modification, any schemas, IDLs, or code samples that are included in the documentation. This permission also applies to any documents that are referenced in the Open Specifications documentation. § No Trade Secrets. Microsoft does not claim any trade secret rights in this documentation.
§ Patents. Microsoft has patents that might cover your implementations of the technologies described in the Open Specifications documentation. Neither this notice nor Microsoft's delivery of this documentation grants any licenses under those patents or any other Microsoft patents. However, a given Open Specifications document might be covered by the Microsoft Open Specifications Promise or the Microsoft Community Promise. If you would prefer a written license, or if the technologies described in this documentation are not covered by the Open Specifications Promise or Community Promise, as applicable, patent licenses are available by contacting [email protected]. § Trademarks. The names of companies and products contained in this documentation might be covered by trademarks or similar intellectual property rights. This notice does not grant any licenses under those rights. For a list of Microsoft trademarks, visit www.microsoft.com/trademarks. § Fictitious Names. The example companies, organizations, products, domain names, email addresses, logos, people, places, and events that are depicted in this documentation are fictitious. No association with any real company, organization, product, domain name, email address, logo, person, place, or event is intended or should be inferred.
1 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 Reservation of Rights. All other rights are reserved, and this notice does not grant any rights other than as specifically described above, whether by implication, estoppel, or otherwise. Tools. The Open Specifications documentation does not require the use of Microsoft programming tools or programming environments in order for you to develop an implementation. If you have access to Microsoft programming tools and environments, you are free to take advantage of them. Certain Open Specifications documents are intended for use in conjunction with publicly available standards specifications and network programming art and, as such, assume that the reader either is familiar with the aforementioned material or has immediate access to it.
2 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 Revision Summary Revision Revision Date History Class Comments
8/8/2013 1.0 New Released new document.
No changes to the meaning, language, or formatting of the 11/14/2013 1.0 None technical content.
No changes to the meaning, language, or formatting of the 2/13/2014 1.0 None technical content.
No changes to the meaning, language, or formatting of the 5/15/2014 1.0 None technical content.
No changes to the meaning, language, or formatting of the 6/30/2015 1.0 None technical content.
No changes to the meaning, language, or formatting of the 7/14/2016 1.0 None technical content.
3/16/2017 2.0 Major Significantly changed the technical content.
3 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 Table of Contents
4 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 1 Introduction The Server and File Management Web APIs Protocol is designed to enable access to and management of the server. It also allows users to access files through Web APIs over the Internet or intranet. Sections 1.5, 1.8, 1.9, 2, and 3 of this specification are normative. All other sections and examples in this specification are informative.
1.1 Glossary This document uses the following terms: base64 encoding: A binary-to-text encoding scheme whereby an arbitrary sequence of bytes is converted to a sequence of printable ASCII characters, as described in [RFC4648]. Distributed File System (DFS): A file system that logically groups physical shared folders located on different servers by transparently connecting them to one or more hierarchical namespaces. DFS also provides fault- tolerance and load-sharing capabilities. DFS refers to the Microsoft DFS available in Windows Server operating system platforms. globally unique identifier (GUID): A term used interchangeably with universally unique identifier (UUID) in Microsoft protocol technical documents (TDs). Interchanging the usage of these terms does not imply or require a specific algorithm or mechanism to generate the value. Specifically, the use of this term does not imply or require that the algorithms described in [RFC4122] or [C706] must be used for generating the GUID. See also universally unique identifier (UUID). Hypertext Transfer Protocol Secure (HTTPS): An extension of HTTP that securely encrypts and decrypts web page requests. In some older protocols, "Hypertext Transfer Protocol over Secure Sockets Layer" is still used (Secure Sockets Layer has been deprecated). For more information, see [SSL3] and [RFC5246]. Secure Sockets Layer (SSL): A security protocol that supports confidentiality and integrity of messages in client and server applications that communicate over open networks. SSL uses two keys to encrypt data-a public key known to everyone and a private or secret key known only to the recipient of the message. SSL supports server and, optionally, client authentication (2) using X.509 certificates (2). For more information, see [X509]. The SSL protocol is precursor to Transport Layer Security (TLS). The TLS version 1.0 specification is based on SSL version 3.0 [SSL3]. security identifier (SID): An identifier for security principals in Windows that is used to identify an account or a group. Conceptually, the SID is composed of an account authority portion (typically a domain) and a smaller integer representing an identity relative to the account authority, termed the relative identifier (RID). The SID format is specified in [MS-
5 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 DTYP] section 2.4.2; a string representation of SIDs is specified in [MS- DTYP] section 2.4.2 and [MS-AZOD] section 1.1.1.2. Stock Keeping Unit (SKU): A unique code that refers to a particular manufactured object or source of revenue. A SKU can refer to a retail product (software in a box that is sold through a channel), a subscription program (such as MSDN), or an online service (such as MSN). Uniform Resource Identifier (URI): A string that identifies a resource. The URI is an addressing mechanism defined in Internet Engineering Task Force (IETF) Uniform Resource Identifier (URI): Generic Syntax [RFC3986]. user principal name (UPN): A user account name (sometimes referred to as the user logon name) and a domain name that identifies the domain in which the user account is located. This is the standard usage for logging on to a Windows domain. The format is: [email protected] (in the form of an email address). In Active Directory, the userPrincipalName attribute (2) of the account object, as described in [MS-ADTS]. XML: The Extensible Markup Language, as described in [XML1.0]. MAY, SHOULD, MUST, SHOULD NOT, MUST NOT: These terms (in all caps) are used as defined in [RFC2119]. All statements of optional behavior use either MAY, SHOULD, or SHOULD NOT.
1.2 References Links to a document in the Microsoft Open Specifications library point to the correct section in the most recently published version of the referenced document. However, because individual documents in the library are not updated at the same time, the section numbers in the documents may not match. You can confirm the correct section numbering by checking the Errata.
1.2.1 Normative References We conduct frequent surveys of the normative references to assure their continued availability. If you have any issue with finding a normative reference, please contact [email protected]. We will assist you in finding the relevant information. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997, http://www.rfc- editor.org/rfc/rfc2119.txt
[RFC2616] Fielding, R., Gettys, J., Mogul, J., et al., "Hypertext Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999, http://www.rfc- editor.org/rfc/rfc2616.txt
[RFC4346] Dierks, T., and Rescorla, E., "The Transport Layer Security (TLS) Protocol Version 1.1", RFC 4346, April 2006, http://www.ietf.org/rfc/rfc4346.txt
6 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 [WSDL] Christensen, E., Curbera, F., Meredith, G., and Weerawarana, S., "Web Services Description Language (WSDL) 1.1", W3C Note, March 2001, http://www.w3.org/TR/2001/NOTE-wsdl-20010315
[XMLNS] Bray, T., Hollander, D., Layman, A., et al., Eds., "Namespaces in XML 1.0 (Third Edition)", W3C Recommendation, December 2009, http://www.w3.org/TR/2009/REC-xml-names-20091208/
[XMLSCHEMA1] Thompson, H., Beech, D., Maloney, M., and Mendelsohn, N., Eds., "XML Schema Part 1: Structures", W3C Recommendation, May 2001, http://www.w3.org/TR/2001/REC-xmlschema-1-20010502/
[XMLSCHEMA2] Biron, P.V., Ed. and Malhotra, A., Ed., "XML Schema Part 2: Datatypes", W3C Recommendation, May 2001, http://www.w3.org/TR/2001/REC-xmlschema-2-20010502/
1.2.2 Informative References None.
1.3 Overview The Server and File Management Web APIs Protocol is used to access a REST- based server and for file management over the HTTPS transports. The protocol exposes a set of built-in web services for third-party developers to build applications on different devices that can access files and manage the server remotely. The protocol also allows third-party developers to add their own web services without the need to handle authentication.
1.4 Relationship to Other Protocols The following figure shows the relationship of this protocol to industry-standard protocols.
Figure 1: Relationship of Server and File Management Web APIs Protocol to industry-standard protocols
7 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 1.5 Prerequisites/Preconditions All web services that are exposed in this protocol are hosted in Internet Information Services (IIS) 7.0 so that a user can call web services by using the Hypertext Transfer Protocol over Secure Sockets Layer (HTTPS) protocol. Secure Sockets Layer (SSL) is required for secure communication.
1.6 Applicability Statement This protocol defines a set of server and file management REST APIs. This protocol is applicable to both Internet and intranet client-server scenarios.
1.7 Versioning and Capability Negotiation This protocol does not provide any mechanism for capability negotiation.
1.8 Vendor-Extensible Fields None.
1.9 Standards Assignments None.
8 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 2 Messages
2.1 Transport This protocol consists of a set of RESTful (representational state transfer) web services. HTTPS over TCP/IP, as specified in [RFC2616]. All client messages to the server MUST use HTTPS. Protocol messages MUST be formatted as specified either in XML or in Javascript Object Notation (JSON). Protocol server faults MUST be returned by using HTTP status codes as specified in [RFC2616], section 10, "Status Code Definitions".
2.2 Common Data Types This section contains common definitions that are used by this protocol. The syntax of the definitions uses an XML Schema, as specified in [XMLSCHEMA1] and [XMLSCHEMA2], and WSDL, as specified in [WSDL].
2.2.1 Namespaces This specification defines and references various XML namespaces by using the mechanisms specified in [XMLNS]. Although this specification associates a specific XML namespace prefix for each XML namespace that is used, the choice of any particular XML namespace prefix is implementation-specific and not significant for interoperability. Prefix NameSpaces URI Reference xs http://www.w3.org/2001/XMLSchema [XMLSCHEM A] tns1 http://contracts.microsoft.com/WindowsServerEssentials/2011/09/WebApi tns2 http://schemas.datacontract.org/2004/07/Microsoft.WindowsServerSolutions.Storage tns4 http://schemas.microsoft.com/2003/10/Serialization/Arrays tns5 http://schemas.microsoft.com/2003/10/Serialization/ tns6 http://schemas.datacontract.org/2004/07/Microsoft.WindowsServerSolutions.AzureADO bjectModel tns7 http://schemas.datacontract.org/2004/07/System.Collections.ObjectModel tns8 http://schemas.datacontract.org/2004/07/Microsoft.WindowsServerSolutions.WebApi.M anagement.Storage tns9 http://schemas.datacontract.org/2004/07/Microsoft.WindowsServerSolutions.O365Integ ration tns10 http://schemas.microsoft.com/Message
2.2.2 HTTP Headers The following table summarizes the set of HTTP headers defined by this protocol.
9 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 The client MUST either pass Canary header or pass AppName, AppPublisherName, AppVersion, and Authorization to a server when the client calls an API that needs authentication information. Header Description
Accept Specifies the acceptable data format for the response. See section 2.2.2.6
AppName Defines the client application name. See section 2.2.2.1
AppPublisherName Defines the client application publisher name. See section 2.2.2.2
AppVersion Defines the client application version. See section 2.2.2.3
Authorization Defines the user authorization. See section 2.2.2.4
Canary Defines a user token returned in the Login response header. See section 2.2.2.5
Range Defines the client request only part of an entity. Bytes are numbered from 0. See section 2.2.2.7.
2.2.2.1 AppName The AppName header defines the client application name.
3 String = *(%x20-7E)
4 AppName = String
5
5.1.1.1 AppPublisherName The AppPublisherName header defines the client application publisher name.
6 String = *(%x20-7E)
7 AppPublisherName = String
8
8.1.1.1 AppVersion The AppVersion header defines the client application version.
9 String = *(%x20-7E)
10 AppVersion = String
11
11.1.1.1 Authorization The Authorization header specifies the user authorization credentials. The client sends requests with an authorization header, the value of which starts with "Basic", followed by a blank space and a base64 encoded string that represents the user name and password separated by a colon.
12 String = *(%x20-7E)
10 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 13 Authorization = String
14
14.1.1.1 Canary The Canary header is a user token that is returned in the Login response header. The client MUST either pass this header or pass AppName, AppPublisherName, AppVersion, and Authorization to the server.
15 String = *(%x20-7E)
16 Canary = String
17
17.1.1.1 Accept The Accept request-header field defines the data format that is acceptable for the response. The format of the Accept header is as follows: Accept: "application/json" / "application/xml"
18 String = *(%x20-7E)
19 Accept = String
20
20.1.1.1 Range Defines the client request only part of an entity. Bytes are numbered from 0. This is a standard http header defined in [RFC2616], section 14.35.1, "Byte Ranges"
21 String = *(%x20-7E)
22 Range = String
23
23.1.1 Common URI Parameters The following table summarizes the set of Common URI parameters defined by this protocol. URI parameters are not case sensitive. URI parameter Description alertkey See section 2.2.3.1 amount See section 2.2.3.2 ascending See section 2.2.3.3 containerpath See section 2.2.3.4 count See section 2.2.3.5
11 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 URI parameter Description deletecontents See section 2.2.3.6 description See section 2.2.3.7 deviceid See section 2.2.3.8 email See section 2.2.3.9 emails See section 2.2.3.10 filter See section 2.2.3.11 firstname See section 2.2.3.12 groupguid See section 2.2.3.13 groupingdata See section 2.2.3.14 groupingmethoddata See section 2.2.3.15 heightdata See section 2.2.3.16 id See section 2.2.3.17 index See section 2.2.3.18 isoriginaldata See section 2.2.3.19 keywords See section 2.2.3.20 language See section 2.2.3.21 lastname See section 2.2.3.22 localusername See section 2.2.3.23 mediatypedata See section 2.2.3.24 name See section 2.2.3.25 newname See section 2.2.3.26 newpath See section 2.2.3.27 onlineusername See section 2.2.3.28 originalpath See section 2.2.3.29 overwrite See section 2.2.3.30 overwritepermissions See section 2.2.3.31 path See section 2.2.3.32 permission See section 2.2.3.33 query See section 2.2.3.34 remotewebaccess See section 2.2.3.35 requestedcountdata See section 2.2.3.36 scope See section 2.2.3.37 servername See section 2.2.3.38 shallowdata See section 2.2.3.39 sharename See section 2.2.3.40 sizedata See section 2.2.3.41 sortbyfield See section 2.2.3.42 sortorderdata See section 2.2.3.43 sortpropertydata See section 2.2.3.44
12 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 URI parameter Description startingindex See section 2.2.3.45 startingindexdata See section 2.2.3.46 timeoutseconds See section 2.2.3.47 titleonlydata See section 2.2.3.48 usergroups See section 2.2.3.49 userid See section 2.2.3.50 username See section 2.2.3.51 usersid See section 2.2.3.52 vpnaccess See section 2.2.3.53 widthdata See section 2.2.3.54
23.1.1.1 alertkey The key of an Alert instance. This parameter MUST be included in alert instance operation.
24 String = *(%x20-7E)
25 alertkey = String
26
26.1.1.1 amount The amount parameter defines the number of items to be retrieved. It SHOULD be a string that can be converted to a positive integer.
27 String = *(%x20-7E)
28 amount = String
29
29.1.1.1 ascending The ascending parameter is a Boolean value that indicates whether the sorting is ascending.
30 String = *(%x20-7E)
31 ascending = String
32
32.1.1.1 containerpath The containerpath parameter describes the path to the container. To specify the root container, leave this parameter empty.
33 String = *(%x20-7E)
13 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 34 containerpath = String
35
35.1.1.1 count The count parameter describes the number of items to be retrieved.
36 String = *(%x20-7E)
37 count = String
38
38.1.1.1 deletecontents This is a flag that indicates whether the contents of the shared folder have been deleted when the folder is no longer shared. Set the flag to TRUE to end sharing the folder and to delete the folder contents. Set the flag to FALSE to end sharing the folder without deleting its contents.
39 String = *(%x20-7E)
40 deletecontents = String
41
41.1.1.1 description The description parameter defines user-friendly description information.
42 String = *(%x20-7E)
43 description = String
44
44.1.1.1 deviceid The deviceid parameter defines the ID of device. It SHOULD be the security identifier (SID) of the device.
45 String = *(%x20-7E)
46 deviceid = String
47
47.1.1.1 email The email parameter defines the user's email address.
48 String = *(%x20-7E)
14 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 49 email = String
50
50.1.1.1 emails This parameter defines an array of email addresses.
51 String = *(%x20-7E)
52 emails = String
53
53.1.1.1 filter This parameter defines the type of the files to be retrieved. It MUST be All, Multimedia, or Document.
54 String = *(%x20-7E)
55 filter = String
56
56.1.1.1 firstname Defines the first name of the user.
57 String = *(%x20-7E)
58 firstname = String
59
59.1.1.1 groupguid Defines the he GUID of the Group, which is specified in section 2.2.5.2.
60 String = *(%x20-7E)
61 groupguid = String
62
62.1.1.1 groupingdata The groupingdata parameter describes the container path. To specify the root container, leave this parameter empty.
63 String = *(%x20-7E)
64 groupingdata = String
65
15 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 65.1.1.1 groupingmethoddata The groupingmethoddata parameter describes the grouping method. Choose from one of the following values. Grouping Method Value Applicable Media Types Meaning album music Group by album. albumartist music Group by album artist. all music, photo, or video Group by media type. artist music Group by artist. date photo Group by date. folder photo or video Group by folder. genre music Group by musical genre (style). playlist music Group by playlist. rating music Group by rating.
66 String = *(%x20-7E)
67 groupingmethoddata = String
68
68.1.1.1 heightdata The heightdata parameter describes the height of an image.
69 String = *(%x20-7E)
70 heightdata = String
71
71.1.1.1 id The id parameter describes the identifier of the item.
72 String = *(%x20-7E)
73 id = String
74
74.1.1.1 index The index parameter defines the numerical position of the first item to be retrieved.
75 String = *(%x20-7E)
76 index = String
77
16 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 77.1.1.1 isoriginaldata The isoriginaldata parameter describes whether to return the orginal data. If this parameter is set, the widthdata and heightdata parameters will not take effect, although they are still required in the request.
78 String = *(%x20-7E)
79 isoriginaldata = String
80
80.1.1.1 keywords The keywords parameter describes a space-separated list of keywords to search for.
81 String = *(%x20-7E)
82 keywords = String
83
83.1.1.1 language This parameter defines the language/region code (such as en-us) of the new folder name.
84 String = *(%x20-7E)
85 language = String
86
86.1.1.1 lastname This parameter defines the last name of the user.
87 String = *(%x20-7E)
88 lastname = String
89
89.1.1.1 localusername This parameter defines the local name of the user.
90 String = *(%x20-7E)
91 localusername = String
92
17 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 92.1.1.1 mediatypedata The mediatypedata parameter describes the media type. Choose from one of the following values. Media Type Value Meaning music Audio clips. photo Photos. video Video clips.
93 String = *(%x20-7E)
94 mediatypedata = String
95
95.1.1.1 name This parameter describes the name of item.
96 String = *(%x20-7E)
97 name = String
98
98.1.1.1 newname The newname parameter describes the new name of the item.
99 String = *(%x20-7E)
100 newname = String
101
101.1.1.1 newpath The newpath parameter describes the network path that begins with the server name, in the format /ServerName/FolderPath.
102 String = *(%x20-7E)
103 newpath = String
104
104.1.1.1 onlineusername This parameter defines the online user’s name.
105 String = *(%x20-7E)
106 onlineusername = String
107
18 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 107.1.1.1 originalpath The originalpath parameter is a network path that begins with the server name, in the format /ServerName/FolderPath.
108 String = *(%x20-7E)
109 originalpath = String
110
110.1.1.1 overwrite The overwrite flag indicates whether to overwrite the item. It SHOULD be either TRUE or FALSE.
111 overwrite = TRUE | FALSE
112
112.1.1.1 overwritepermissions This is a flag that indicates whether to overwrite the descriptions on the server folder. It SHOULD be a string of TRUE or FALSE.
113 overwritepermissions = TRUE | FALSE
114
114.1.1.1 path This parameter is the path of directory or file. If it is a network path that begins with the server name, it is in this format: \\ServerName\FolderPath If it is a local path, the format is as follows: C:\folderName\ItemName
115 String = *(%x20-7E)
116 path = String
117
117.1.1.1 permission The permissions parameter defines the user access permissions on a shared folder. The value SHOULD be a string that can be converted to one of following integers: § 0: None, no access. § 1: ReadOnly, read-only access. § 2: Full, read/write access. § 3: Other, unknown or unspecified access.
19 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 118 String = *(%x20-7E)
119 permission = String
120
120.1.1.1 query This parameter defines the string to search for within the names of the files and folders.
121 String = *(%x20-7E)
122 query = String
123
123.1.1.1 remotewebaccess This flag indicates whether to allow the user to have remote web access. It SHOULD be either TRUE (to allow the user to have remote web access) or FALSE.
124 String = *(%x20-7E)
125 remotewebaccess = String
126
126.1.1.1 requestedcountdata The requestedcountdata parameter describes the requested number of media items to be retrieved.
127 String = *(%x20-7E)
128 requestedcountdata = String
129
129.1.1.1 scope This is the UNC path of the folder in which the search is performed.
130 String = *(%x20-7E)
131 scope = String
132
132.1.1.1 servername This parameter identifies the server name.
133 String = *(%x20-7E)
20 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 134 servername = String
135
135.1.1.1 shallowdata The shallowdata parameter describes whether the search is shallow or deep.
136 String = *(%x20-7E)
137 shallowdata = String
138
138.1.1.1 sharename This is the name of the shared folder. It cannot contain the following characters: § < (less than) § >(greater than) § : (colon) § " (double quote) § / (forward slash) § \ (backslash) § | (vertical bar or pipe) § ? (question mark) § * (asterisk)
139 String = *(%x20-7E)
140 sharename = String
141
141.1.1.1 sizedata The sizedata parameter describes the size of the test data to be retrieved.
142 String = *(%x20-7E)
143 sizedata = String
144
144.1.1.1 sortbyfield This is the field of the file item property by which file items are sorted.
145 String = *(%x20-7E)
146 sortbyfield = String
147
21 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 147.1.1.1 sortorderdata The sortorderdata parameter describes the sort order. The following values are allowed. Sort Order Value Meaning
ASC Sort in ascending order. default Sort in the default sort order.
DESC Sort in descending order.
148 String = *(%x20-7E)
149 sortorderdata = String
150
150.1.1.1 sortpropertydata The sortpropertydata parameter describes the metadata property on which to sort the media items. The following values are allowed. Metadata Property Type Meaning date Sort by date. default Sort by the default metadata property type in the web service. title Sort by title.
151 String = *(%x20-7E)
152 sortpropertydata = String
153
153.1.1.1 startingindex The startingindex parameter is the numerical position of the first item to be retrieved. It SHOULD be a string that can be converted to a positive integer.
154 String = *(%x20-7E)
155 startingindex = String
156
156.1.1.1 startingindexdata The startingindexdata parameter describes the numerical position of the first media item to be retrieved.
157 String = *(%x20-7E)
158 startingindexdata = String
159
22 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 159.1.1.1 timeoutseconds The timeoutseconds parameter defines the number of seconds after which the request times out.
160 String = *(%x20-7E)
161 timeoutseconds = String
162
162.1.1.1 titleonlydata The titleonlydata parameter describes whether the search is performed on the title only. If this parameter is not specified, the default value is FALSE.
163 String = *(%x20-7E)
164 titleonlydata = String
165
165.1.1.1 usergroups The usergroups parameter is a list of the group GUIDs separated by commas, as specified in section 2.2.5.2.
166 String = *(%x20-7E)
167 usergroups = String
168
168.1.1.1 userid The userid identifies the user. It SHOULD be a SID.
169 String = *(%x20-7E)
170 userid = String
171
171.1.1.1 username The username parameter defines the user name and SHOULD be the logon name of the user.
172 String = *(%x20-7E)
173 username = String
174
174.1.1.1 usersid This parameter defines the security identifier (SID) of a user.
23 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 175 String = *(%x20-7E)
176 usersid = String
177
177.1.1.1 vpnaccess This is a flag that indicates whether to allow the user to have access to a virtual private network (VPN). It is set to TRUE to allow a user to have access to a VPN; otherwise, it is set to FALSE.
178 String = *(%x20-7E)
179 vpnaccess = String
180
180.1.1.1 widthdata The widthdata parameter describes the width of an image.
181 String = *(%x20-7E)
182 widthdata = String
183
183.1.1 Complex Types The following table summarizes the set of common XML Schema complex type definitions defined by this specification. Complex Type Description
AlertInfo The AlertInfo type contains informational data about a Network Health Alert.
ArrayOfAlertInfo This type describes an array of AlertInfo.
ArrayOfConnectionInfo This type describes an array of ConnectionInfo.
ArrayOfDeviceInfo This type describes an array of DeviceInfo.
ArrayOfDriveInfo This type describes an array of DriveInfo.
ArrayOfFolderInfo This type describes an array of FolderInfo.
ArrayOfGroupInfo This type describes an array of GroupInfo.
ArrayOfItemInfo This type describes an array of ItemInfo.
ArrayOfLink This type describes an array of Link.
ArrayOfMailbox This type describes an array of Mailbox.
ArrayOfMetadataBase This type describes an array of MetadataBase.
ArrayOfMetadataItemStream This type describes an array of MetadataItemStream.
ArrayOfMSODomain This type describes an array of MSODomain.
ArrayOfMSOLicense This type describes an array of MSOLicense.
ArrayOfMSOLicenseService This type describes an array of MSOLisenseService.
24 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 Complex Type Description
ArrayOfMSOLicenseSubscription This type describes an array of MSOLicenseSubscription.
ArrayOfMSOLicenseSuite This type contains the license suite information for the online service.
ArrayOfMSOUser This type describes an array of MSOUser.
ArrayOfStorageDriveInfo This type describes an array of StorageDriveInfo.
ArrayOfStorageServerInfo This type describes an array of StorageServerInfo.
ArrayOfstring This type describes an array of string.
ArrayOfUserInfo This type describes an array of UserInfo.
ArrayOfWebApiProvider This type describes an array of WebApiProvider.
CompanyAddress The CompanyAddress type contains the address of the company.
ConnectionClientInfo The ConnectionClientInfo type contains client information of the connection instance.
ConnectionInfo The ConnectionInfo type contains user connection data information.
CustomizationInfo The CustomizationInfo type contains customization data information.
DeviceInfo The DeviceInfo type contains informational data about the device that is managed byWindows.
DriveInfo The DriveInfo type contains informational data about the server drive.
FolderInfo The FolderInfo type contains informational data about the folder that is managed by the server.
GroupInfo The GroupInfo type contains informational data about the group.
ItemInfo The file item metadata.
ItemList The collection of the file item metadata.
ItemThumbnail The ItemThumbnail type contains informational data about Thumbnail.
Link The Link type contains informational data about the customization link.
Mailbox The Mailbox type contains information about the mailbox.
MetadataBase The MetadataBase type is the base type for all the metadata of all the media content.
MetadataContainer The MetadataContainer type describes the container for media content.
MetadataDetailResult The MetadataDetailResult describes the detail information for the metadata container.
MetadataItem The MetadataItem type contains the definition of the specific media item.
MetadataItemStream The MetadataItemStream type describes the stream information of the media item.
MetadataResult The MetadataResult type contains a list of media items and media containers, together with the total number that matches the query request.
MetadataStreamResult The MetadataStreamResult type contains a list of
25 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 Complex Type Description
media stream items, together with the count number of streams for the specified media items.
Office365Mailbox The Office365Mailbox type contains the information about the Office 365 mailbox.
ExchangeServerMailbox The ExchangeServerMailbox type contains the information about the Exchange mailbox.
HostedMailbox The HostedMailbox type contains the information about the hosted mailbox.
MSODomain The MSODomain type contains the domain information for the online service.
MSOLicense The MSOLicense type contains the license information for the online service
MSOLicenseService The MSOLicenseService type contains the license type information for the online service
MSOLicenseSubscription The MSOLicenseSubscription type contains the license subscription information for the online service.
MSOLicenseSuite The MSOLicenseSuite type contains the license suite information for the online service.
MSOTenantInformation The MSOTenantInformation type contains the tenant information for the online service.
MSOUser The MSOUser type contains the user information for the online service.
PartialCollection_Of_AlertInfo This type describes a partial collection of AlertInfo.
PartialCollection_Of_ConnectionInfo This type describes a partial collection of ConnectionInfo.
PartialCollection_Of_DeviceInfo This type describes a partial collection of DeviceInfo.
PartialCollection_Of_DriveInfo This type describes a partial collection of DriveInfo.
PartialCollection_Of_FolderInfo This type describes a partial collection of FolderInfo.
PartialCollection_Of_UserInfo This type describes a partial collection of UserInfo.
ReadOnlyCollectionOfGroupInfoEV6sb80H This type describes a read-only connection of GroupInfo.
ReadOnlyCollectionOfMSOLicensepPGX_Pb6b This type describes a read-only connection of MSOLicense.
ReadOnlyCollectionOfMSOLicenseServicepPGX_Pb6b This type describes a read-only connection of MSOLicenseService.
ReadOnlyCollectionOfMSOLicenseSubscriptionpPGX_Pb6b This type describes a read-only connection of MSOLicenseSubscription.
ReadOnlyCollectionOfMSOLicenseSuitepPGX_Pb6b This type describes a read-only collection of MSOLicenseSuite as specified in section 2.2.4.51.
RemoteConnectionUserInfo The RemoteConnectionUserInfo type contains user information about the remote connection.
SearchItemList The collection of searched file item metadata.
ServerInfo The ServerInfo type contains informational data about the server.
SharePointSiteAddressCollection The SharePointSiteAddressCollection type contains the SharePoint site addresses.
StorageDriveInfo This type contains information about the drive used to create the storage folder (see section 2.2.4.30).
26 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 Complex Type Description
StorageServerInfo This type contains information about the server used to create the storage folder.
UserInfo The UserInfo type contains informational data about the user.
WebApiProvider The WebApiProvider type contains informational data about the WebApi provider.
183.1.1.1 AlertInfo The AlertInfo type contains informational data about a Network Health Alert. Namespace: http://contracts.microsoft.com/WindowsServerEssentials/2011/09/WebApi
184
185
186
187
188
189
190
191
192
193
194
195
196
CanRepair: If the alert is repairable, this is set to TRUE; otherwise, FALSE. DateAndTime: The date and time when the alert was raised. Description: The description of the alert. IsSuppressed: If the alert is suppressed, this is set to TRUE; otherwise, FALSE. Key: The key of the alert. MachineName: The name of the machine on which the alert is raised. Severity: The health status.
27 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 Title: The name of the feature definition for which the alert is raised. TroubleshootingSteps: The troubleshooting steps of the alert.
196.1.1.1 ArrayOfAlertInfo This type describes an array of AlertInfo. Namespace: http://contracts.microsoft.com/WindowsServerEssentials/2011/09/WebApi
197
198
199
200
201
AlertInfo: The instance of AlertInfo. See section 2.2.4.1
201.1.1.1 ArrayOfConnectionInfo This type describes an array of ConnectionInfo. Namespace: http://contracts.microsoft.com/WindowsServerEssentials/2011/09/WebApi
202
203
204
205
206
ConnectionInfo: The connection information instance.
206.1.1.1 ArrayOfDeviceInfo This type describes an array of DeviceInfo. Namespace: http://contracts.microsoft.com/WindowsServerEssentials/2011/09/WebApi
207
208
209
210
28 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 211
DeviceInfo: The instance of DeviceInfo, as specified in section 2.2.4.28.
211.1.1.1 ArrayOfDriveInfo This type describes an array of DriveInfo. Namespace: http://contracts.microsoft.com/WindowsServerEssentials/2011/09/WebApi
212
213
214
215
216
DriveInfo: The instance of DriveInfo, as specified in section 2.2.4.29.
216.1.1.1 ArrayOfFolderInfo This type describes an array of FolderInfo. Namespace: http://contracts.microsoft.com/WindowsServerEssentials/2011/09/WebApi
217
218
219
220
221
FolderInfo: The instance of FolderInfo, as specified in section 2.2.4.30.
221.1.1.1 ArrayOfGroupInfo This type describes an array of GroupInfo. Namespace: http://contracts.microsoft.com/WindowsServerEssentials/2011/09/WebApi
222
223
224
29 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 225
226
GroupInfo: The instance of Group, as specified in section 2.2.4.31.
226.1.1.1 ArrayOfItemInfo This type describes an array of ItemInfo. Namespace: http://contracts.microsoft.com/WindowsServerEssentials/2011/09/WebApi
227
228
229
230
231
ItemInfo: The instance of ItemInfo as specified in section 2.2.4.32.
231.1.1.1 ArrayOfLink This type describes an array of Link. Namespace: http://contracts.microsoft.com/WindowsServerEssentials/2011/09/WebApi
232
233
234
235
236
Link: The instance of Link type represents the customization link information, as specified in section 2.2.4.35.
236.1.1.1 ArrayOfMailbox This type describes an array of Mailbox. Namespace: http://contracts.microsoft.com/WindowsServerEssentials/2011/09/WebApi
237
238
30 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 239
240
241
Mailbox: The instance of Mailbox, as specified in section 2.2.4.36.
241.1.1.1 ArrayOfMetadataBase This type describes an array of MetadataBase.<1> Namespace: http://contracts.microsoft.com/WindowsServerEssentials/2011/09/WebApi
242
243
244
245
246
MetadataBase: The instance of Metadata, as specified in section 2.2.4.40.
246.1.1.1 ArrayOfMetadataItemStream This type describes an array of MetadataItemStream as specified in section 2.2.4.44.<2> Namespace: http://contracts.microsoft.com/WindowsServerEssentials/2011/09/WebApi
247
248
249
250
251
MetadataItemStream: Describes the stream information of the media item.
251.1.1.1 ArrayOfMSODomain This type describes an array of MSODomain, specified in section 2.2.4.47. Namespace: http://schemas.datacontract.org/2004/07/Microsoft.WindowsServerSolutions.A zureADObjectModel
31 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 252
253
254
255
256
MSODomain: An instance of MSODomain.
256.1.1.1 ArrayOfMSOLicense This type describes an array of MSOLicense, specified in section 2.2.4.48. Namespace: http://schemas.datacontract.org/2004/07/Microsoft.WindowsServerSolutions.A zureADObjectModel
257
258
259
260
261
MSOLicense: The instance of MSOLicense.
261.1.1.1 ArrayOfMSOLicenseService This type describes an array of MSOLicenseService specified in section 2.2.4.49. Namespace: http://schemas.datacontract.org/2004/07/Microsoft.WindowsServerSolutions.A zureADObjectModel
262
263
264
265
266
MSOLicenseService: The instance of MSOLicenseService.
32 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 266.1.1.1 ArrayOfMSOLicenseSubscription This type describes an array of MSOLicenseSubscription, specified in section 2.2.4.50. Namespace: http://schemas.datacontract.org/2004/07/Microsoft.WindowsServerSolutions.A zureADObjectModel
267
268
269
270
271
MSOLicenseSubscription: The instance of MSOLicenseSubscription.
271.1.1.1 ArrayOfMSOLicenseSuite This type describes an array of MSOLicenseSuite, specified in section 2.2.4.51. Namespace: http://schemas.datacontract.org/2004/07/Microsoft.WindowsServerSolutions.A zureADObjectModel
272
273
274
275
276
MSOLicenseSuite: The instance of MSOLicenseSuite.
276.1.1.1 ArrayOfMSOUser This type describes an array of MSOUser, specified in section 2.2.4.53. Namespace: http://schemas.datacontract.org/2004/07/Microsoft.WindowsServerSolutions.A zureADObjectModel
277
278
279
280
33 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 281
MSOUser: The instance of MSOUser.
281.1.1.1 ArrayOfStorageDriveInfo This type describes an array of StorageDriveInfo. Namespace: http://contracts.microsoft.com/WindowsServerEssentials/2011/09/WebApi
282
283
284
285
286
StorageDriveInfo: The instance of StorageDriveInfo. See section 2.2.4.69
286.1.1.1 ArrayOfStorageServerInfo This type describes an array of storageServerInfo. Namespace: http://contracts.microsoft.com/WindowsServerEssentials/2011/09/WebApi
287
288
289
290
291
StorageServerInfo: The instance of StorageServerInfo. See section 2.2.4.70
291.1.1.1 ArrayOfstring This type describes an array of string. Namespace: http://schemas.microsoft.com/2003/10/Serialization/Arrays
292
293
294
295
34 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 296 string: The instance of string.
296.1.1.1 ArrayOfUserInfo This type describes an array of UserInfo. Namespace: http://contracts.microsoft.com/WindowsServerEssentials/2011/09/WebApi
297
298
299
300
301
UserInfo: The instance of UserInfo. See section 2.2.4.71
301.1.1.1 ArrayOfWebApiProvider This type describes an array of WebApiProvider, as specified in section 2.2.4.72. Namespace: http://contracts.microsoft.com/WindowsServerEssentials/2011/09/WebApi
302
303
304
305
306
WebApiProvider: The instance of WebApiProvider. See section 2.2.4.72
306.1.1.1 CompanyAddress This type describes the address of a company. Namespace: http://schemas.datacontract.org/2004/07/Microsoft.WindowsServerSolutions.A zureADObjectModel
307
308
35 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 309
310
311
312
313
314
315
316
City: The city of the company. Country: The country of the company. PostalCode: The postal code of the company. State: The state of the company. Street: The street of the company. TelephoneNumber: The telephone number of the company.
316.1.1.1 ConnectionClientInfo The ConnectionClientInfo type contains client information of the connection instance. Namespace: http://contracts.microsoft.com/WindowsServerEssentials/2011/09/WebApi
317
318
319
320
321
322
323
324
36 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 325
ClientApplicationName: The client application name. ClientApplicationPublisher: The client application publisher information. ClientApplicationVersion: The client application version. ClientHostname: The client host name. ClientIPAddress: The client IP address.
325.1.1.1 ConnectionInfo The ConnectionInfo type contains user connection data information. Namespace: http://contracts.microsoft.com/WindowsServerEssentials/2011/09/WebApi
326
327
328
329
330
331
332
333
334
ClientInfo: The client information of the connection. See section 2.2.4.25. EndTime: The end time of the connection. ServiceType: The service type of the connection. StartTime: The start time of the connection. UserInfo: The user information of the connection. See section 2.2.4.65.
334.1.1.1 CustomizationInfo The CustomizationInfo type contains customization data information. Namespace: http://contracts.microsoft.com/WindowsServerEssentials/2011/09/WebApi
335
336
337
37 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 338
339
340
341
342
BackgroundImage: The URI of the background image. Links: An array that contains customization links. Logo: The URI of the logo. Title: The URI of the title.
342.1.1.1 DeviceInfo The DeviceInfo type contains informational data about a device that is managed by the server. Namespace: http://contracts.microsoft.com/WindowsServerEssentials/2011/09/WebApi
343
344
345
346
347
348
349
350
351
352
353
354
38 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 355
356
357
358
359
360
361
362
363
364
AntiSpywareStatus: The antispyware status of the device. AntiVirusStatus: The antivirus status of the device. BackupProgress: The backup process if the backup status is InProcess. BackupStatus: The backup status of devices. It SHOULD one of these values: § Unknown § Configured § Successful § Failed § Incomplete § InProgress § NotConfigured § InQueue § PreparingForBackup § FinalizingBackup § RecoveryInProgress CanBackup: A flag that indicates whether the device can start backup. DeviceDescription: The description of the device. DeviceName: The name of the device. DeviceType: The type of device, which SHOULD be one of these values: § Unknown § ArchivedClient § Client § SolutionServer FirewallStatus: The firewall status of the device.
39 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 Key: The key of the device. OnlineStatus: The online status of the device, which SHOULD be one of these values: § Unknown § Online § Offline OSFamily: The operating system information, which SHOULD one of these values: § Unknown § WindowsSeverity § Macintosh OSName: The name of the operating system of the device. OSServicePack: The operating system service pack version of the device. SecurityCenterStatus: The security center status of the device. SystemType: The system type of the device, which SHOULD be one of these values: § Unknown § X86 § AMD64 UpdateDetailStatus: The Windows update detail information of the device. UpdateStatus: The Windows update status of the device.
364.1.1.1 DriveInfo The DriveInfo type contains informational data about the server drive. Namespace: http://contracts.microsoft.com/WindowsServerEssentials/2011/09/WebApi
365
366
367
368
369
370
371
372
373
40 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 374
375
376
377
378
379
380
381
Capacity: The total capacity of this drive in bytes. DataStatus: The data status of this drive. DiskID: The unique ID of the parent disk. DriveGuid: The drive GUID, which persists across reboots. FileSystemType: The file system on this drive, which SHOULD be one of the following: § Unknown § Raw § FAT § FAT32 § NTFS § CDFS § UDF § EXFAT § CSVFS § REFS ID: The unique ID of the drive. MountPoint: The mount point of the drive. Name: The user-friendly name of the drive. NextSnapshotTime: The time at which the drive takes the next snapshot. SnapshotsEnabled: A flag that indicates whether snapshots are enabled for this drive. Status: The status of this drive. SystemDrive: A flag that indicates whether the drive is a system drive. UsedSpace: The total used space on this drive in bytes.
41 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 381.1.1.1 FolderInfo The FolderInfo type contains informational data about the folder that is managed by the server. Namespace: http://contracts.microsoft.com/WindowsServerEssentials/2011/09/WebApi
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
AccessPermission: The user access permission on this folder, as specified in section 2.2.5.5. CurrentStatus: The folder status. Description: The user-friendly description of the folder. DriveFreeSpace: The free space of the parent drive. DriveID: The ID of the drive this folder is on.
42 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 FolderType: The folder type. It SHOULD be one of ServerFolderType, see section 2.2.5.6. ID: The unique ID of the folder. Name: The folder name. Path: The local path of the folder. Shared: A flag that indicates whether the folder is shared. SharePath: The share path of this folder. If the folder is not shared, this is NULL. UncPath: The Universal Naming Convention (UNC) path of the folder.
397.1.1.1 GroupInfo The GroupInfo type contains informational data about the group. Namespace: http://contracts.microsoft.com/WindowsServerEssentials/2011/09/WebApi
398
399
400
401
402
403
404
405
406
407
CurrentSid: The SID of the group. GroupName: The name of the group. Guid: The Guid of the group. RemoteWebAccess: A flag that indicates whether the group has remote web access permission. VpnAccess: A flag that indicates whether the group has VPN access permission. WindowsAccount: The Windows account of the group.
407.1.1.1 ItemInfo This is the file item metadata.
43 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 Namespace: http://contracts.microsoft.com/WindowsServerEssentials/2011/09/WebApi
408
409
410
411
412
413
414
415
416
417
418
419
420
AccessPermission: This is a number that represents the current user's access permission to the file item. It MUST be one of the following: 0 (no access), 1 (read-only access), 2 (read/write access), or 3 (unknown or unspecific access).
CreateTime: The time that the file is created.
CreateTimeUtc: The UTC time that the file is created.
IsDirectory: A Boolean value that indicates whether the file item is a directory.
ModifiedTime: The last modified time of the file item.
ModifiedTimeUtc: The last modified UTC time of the file item.
Name: The name of the file item.
Path: The UNC path of the file item.
Size: The size (in bytes) of the file item.
420.1.1.1 ItemList The collection of file item metadata. Namespace: http://contracts.microsoft.com/WindowsServerEssentials/2011/09/WebApi
421
44 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 422
423
424
425
426
Items: The collection of file item metadata. TotalCount: The total count of the matched file items regardless of index and count parameter.
426.1.1.1 ItemThumbnail The ItemThumbnail type contains informational data about the Thumbnail. Namespace: http://contracts.microsoft.com/WindowsServerEssentials/2011/09/WebApi
427
428
429
430
431
432
433
434
Buffer: The raw image buffer. Format: The image format. Height: The image height. Width: The image width.
434.1.1.1 Link The Link type contains informational data about the link that can be customized by the administrator. Namespace: http://contracts.microsoft.com/WindowsServerEssentials/2011/09/WebApi
435
436
45 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 437
438
439
440
Address: The URI of the customizable link. Title: The title of the customizable link.
440.1.1.1 Mailbox The Mailbox type contains the information about the mailbox. Namespace: http://contracts.microsoft.com/WindowsServerEssentials/2011/09/WebApi
441
442
443
444
445
446
Email: The email address. UserName: The local user name.
446.1.1.1 Office365Mailbox The Office365Mailbox type contains the information about the Office 365 mailbox. Namespace: http://contracts.microsoft.com/WindowsServerEssentials/2011/09/WebApi
447
448
449
450
451
452
453
46 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 454
455
Activated: A flag that indicates whether the mailbox is activated.
455.1.1.1 ExchangeServerMailbox The ExchangeServerMailbox type contains the information about the Exchange mailbox. Namespace: http://contracts.microsoft.com/WindowsServerEssentials/2011/09/WebApi
456
457
458
459
460
461
462
463
464
465
Quota: The quota of the mailbox in gigabytes. QuotaEnforced: A flag that indicates whether the quota is enforced.
465.1.1.1 HostedMailbox The HostedMailbox type contains the information about the hosted mailbox. Namespace: http://contracts.microsoft.com/WindowsServerEssentials/2011/09/WebApi
466
467
468
469
470
471
472
47 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 473
474
Enabled: A flag that indicates whether the mailbox is enabled.
474.1.1.1 MetadataBase This is the base type for all the metadata of all the media content, including each specific item and container.<3> Namespace: http://contracts.microsoft.com/WindowsServerEssentials/2011/09/WebApi
475
476
477
478
479
480
481
482
Date: The date of the item. Id: The ID of the item. Title: The title of the item. TypeName: The type name of the item.
482.1.1.1 MetadataContainer The MetadataContainer type describes the container for media content.<4> According to different grouping methods used for browsing, the meaning of the container will be different. For example, if it is grouped by Music Album, then the media item in each container will be the music from the same album. If it is grouped by the folder, then it can be a regular file, and the media item in each container will be the media in the same folder. Namespace: http://contracts.microsoft.com/WindowsServerEssentials/2011/09/WebApi
483
484
48 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 485
486
487
488
489
490
491
492
493
494
495
496
497
AllCount: The count of subcontainers and subitems (recursive). AllDuration: Total duration of subcontainers and subitems (recursive). AllSize: Total size of subcontainers and subtems (recursive). CalculationDone: A flag indicating whether the detail information is available. ContainerType: The type of container. Count: The count of subcontainers and sub-items (nonrecursive). FullPath: The full path for the container when grouping by folder.
497.1.1.1 MetadataDetailResult The MetadataDetailResult type describes the detail information for the metadata container.<5> Namespace: http://contracts.microsoft.com/WindowsServerEssentials/2011/09/WebApi
498
499
500
501
502
49 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 Result: The result of MetadataDetail.
502.1.1.1 MetadataItem The MetadataItem type contains the definition of the specific media item.<6> Namespace: http://contracts.microsoft.com/WindowsServerEssentials/2011/09/WebApi
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
Album: The album of the media item. AlbumArtist: The album artist of the media item. Duration: The duration of the media item. ParentFullPath: The full path of the media item's parent container. Rating: The rating of the media item. Resolution: The resolution of the media item. Size: The size of the media item. Tags: The tags of the media item.
50 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 518.1.1.1 MetadataItemStream The MetadataItemStream type describes the stream information of the media item.<7> Namespace: http://contracts.microsoft.com/WindowsServerEssentials/2011/09/WebApi
519
520
521
522
523
524
525
526
527
528
529
Bitrate: The bitrate of the media stream.
Height: The height of the media stream.
MimeType: The Multipurpose Internet Mail Exchange (MIME) type of the media stream.
Profile: The profile of the media stream.
RelativePath: The relative path of the media stream, which can be used to generate the full path of the media stream.
RequiresTranscoding: Indicates whether this media stream requires transcoding on the server side.
Width: The width of the media stream.
529.1.1.1 MetadataResult The MetadataResult type contains a list of media items and media containers, together with the total number that matches the query request.<8> Namespace: http://contracts.microsoft.com/WindowsServerEssentials/2011/09/WebApi
530
531
51 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 532
533
534
535
Result: A list of media items and media containers. TotalMatches: The total number that matches the query request.
535.1.1.1 MetadataStreamResult The MetadataStreamResult type contains a list of media stream items, together with the number of streams for the specified media items.<9> Namespace: http://contracts.microsoft.com/WindowsServerEssentials/2011/09/WebApi
536
537
538
539
540
541
Result: A list of media stream items. TotalMatches: The count number of streams for the specified media items.
541.1.1.1 MSODomain The MSODomain type contains the domain information for the online service. Namespace: http://schemas.datacontract.org/2004/07/Microsoft.WindowsServerSolutions.A zureADObjectModel
542
543
544
545
546
52 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 547
548
549
CapabilityType: The domain type. IsPrimary: A flag that indicates whether this domain is primary. IsVerified: A flag that indicates whether this domain is verified. Name: The domain name.
549.1.1.1 MSOLicense The MSOLicense type contains the license information for the online service. Namespace: http://schemas.datacontract.org/2004/07/Microsoft.WindowsServerSolutions.A zureADObjectModel
550
551
552
553
554
555
556
AccountName: The account name of the license. Services: The service of the license. SkuId: The SKU ID of the license.
556.1.1.1 MSOLicenseService The MSOLicenseService type contains the license type information for the online service. Namespace: http://schemas.datacontract.org/2004/07/Microsoft.WindowsServerSolutions.A zureADObjectModel
557
558
559
53 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 560
561
562
563
564
Activated: A flag that indicates whether the service is activated. Description: The description of the license. ServicePlan: The service plan for the license. ServiceType: The service type for the license.
564.1.1.1 MSOLicenseSubscription The MSOLicenseSubscription type contains the license subscription information for the online service. Namespace: http://schemas.datacontract.org/2004/07/Microsoft.WindowsServerSolutions.A zureADObjectModel
565
566
567
568
569
570
BillingExpirationTime: The billing expiration time of the subscription. Expired: A flag that indicates whether the subscription is expired.
570.1.1.1 MSOLicenseSuite The MSOLicenseSuite type contains the license suite information for the online service. Namespace: http://schemas.datacontract.org/2004/07/Microsoft.WindowsServerSolutions.A zureADObjectModel
571
572
54 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 573
574
575
576
577
578
579
ConsumedLicenses: The number of consumed licenses. Description: The description of the license. License: The license type included in the license suite. Subscriptions: The collection of the subscriptions for the license suite. TotalLicenses: The total license number of licenses.
579.1.1.1 MSOTenantInformation The MSOTenantInformation type contains the tenant information for the online service. Namespace: http://schemas.datacontract.org/2004/07/Microsoft.WindowsServerSolutions.A zureADObjectModel
580
581
582
583
584
585
586
587
588
55 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 589
590
Activated: A flag that indicates whether the online account is activated for this tenant. Address: The address of the company. CompanyName: The name of the company. InitialDomain: The initial domain. LicenseSuite: The license suite. PrimaryDomain: The primary domain. TechnicalContact: The technical contact information.
590.1.1.1 MSOUser The MSOUser type contains the user information for the online service. Namespace: http://schemas.datacontract.org/2004/07/Microsoft.WindowsServerSolutions.A zureADObjectModel
591
592
593
594
595
596
597
598
599
600
601
Activated: A flag that indicates whether the user is activated. FirstName: The first name of the local user. LastName: The last name of the local user. Licenses: The licenses assigned to the online user. LocalUserName: The local user name.
56 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 ObjectId: The object ID of the online user. UserPrincipalName: The principle name for the user.
601.1.1.1 PartialCollection_Of_AlertInfo This type describes a partial collection of AlertInfo (section 2.2.4.1). If CollectionSize is less than zero, the collection is not available and the CollectionChunk field SHOULD be ignored. Namespace: http://contracts.microsoft.com/WindowsServerEssentials/2011/09/WebApi
602
603
604
605
606
607
608
CollectionChunk: The items retrieved from the overall collection. CollectionModified: The date and time the collection was last changed. CollectionSize: The total number of items in the complete collection.
608.1.1.1 PartialCollection_Of_ConnectionInfo This type describes a partial collection of ConnectionInfo (section 2.2.4.26). If CollectionSize is less than zero, the collection is not available and the CollectionChunk field SHOULD be ignored. Namespace: http://contracts.microsoft.com/WindowsServerEssentials/2011/09/WebApi
609
610
611
612
613
614
615
CollectionChunk: The items retrieved from the overall collection.
57 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 CollectionModified: The date and time the collection last changed. CollectionSize: The total number of items in the complete collection.
615.1.1.1 PartialCollection_Of_DeviceInfo This type describes a partial collection of DeviceInfo (section 2.2.4.28). If CollectionSize is less than zero, the collection is not available and the CollectionChunk field SHOULD be ignored. Namespace: http://contracts.microsoft.com/WindowsServerEssentials/2011/09/WebApi
616
617
618
619
620
621
622
CollectionChunk: The items retrieved from the overall collection. CollectionModified: The date and time the collection last changed. CollectionSize: The total number of items in the complete collection.
622.1.1.1 PartialCollection_Of_DriveInfo This type describes a partial collection of DriveInfo (section 2.2.4.29). If CollectionSize is less than zero, the collection is not available and the CollectionChunk field SHOULD be ignored. Namespace: http://contracts.microsoft.com/WindowsServerEssentials/2011/09/WebApi
623
624
625
626
627
628
629
CollectionChunk: Items retrieved from the overall collection.
58 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 CollectionModified: Date and time the collection last changed. CollectionSize: The total number of items in the complete collection.
629.1.1.1 PartialCollection_Of_FolderInfo This Type describes a partial collection of FolderInfo (section 2.2.4.30). If CollectionSize is less than zero, the collection is not available and the CollectionChunk field SHOULD be ignored. Namespace: http://contracts.microsoft.com/WindowsServerEssentials/2011/09/WebApi
630
631
632
633
634
635
636
CollectionChunk: The items retrieved from the overall collection. CollectionModified: The date and time the collection last changed. CollectionSize: The total number of items in the complete collection.
636.1.1.1 PartialCollection_Of_UserInfo This type describes an partial collection of UserInfo (section 2.2.4.71). If CollectionSize is less than zero, the collection is not available and the CollectionChunk field SHOULD be ignored. Namespace: http://contracts.microsoft.com/WindowsServerEssentials/2011/09/WebApi
637
638
639
640
641
642
643
CollectionChunk: The items retrieved from the overall collection.
59 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 CollectionModified: The date and time the collection changed lastly. CollectionSize: The total number of items in the complete collection.
643.1.1.1 ReadOnlyCollectionOfGroupInfoEV6sb80H This type describes a read-only collection of GroupInfo (section 2.2.4.31). Namespace: http://schemas.datacontract.org/2004/07/System.Collections.ObjectModel
644
645
646
647
648 list: The content of the read-only collection, it contains the list of GroupInfo instances.
648.1.1.1 ReadOnlyCollectionOfMSOLicensepPGX_Pb6b This type describes a read-only collection of MSOLicense (section 2.2.4.48). Namespace: http://schemas.datacontract.org/2004/07/System.Collections.ObjectModel
649
650
651
652
653 list: The content of the read-only collection; it contains the list of MSOLicense instances.
653.1.1.1 ReadOnlyCollectionOfMSOLicenseServicepPGX_Pb6b This type describes a read-only collection of MSOLicenseService (section 2.2.4.49). Namespace: http://schemas.datacontract.org/2004/07/System.Collections.ObjectModel
654
655
60 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 656
657
658 list: The content of the read-only collection; it contains the list of MSOLicenseService instances.
658.1.1.1 ReadOnlyCollectionOfMSOLicenseSubscriptionpPGX_Pb6b This type describes a read-only collection of MSOLicenseSubscription (section 2.2.4.50). Namespace: http://schemas.datacontract.org/2004/07/System.Collections.ObjectModel
659
660
661
662
663 list: The content of the read-only collection; it contains the list of MSOLicenseSubscription instances.
663.1.1.1 ReadOnlyCollectionOfMSOLicenseSuitepPGX_Pb6b This type describes a read-only collection of MSOLicenseSuite as specified in section 2.2.4.51. Namespace: http://schemas.datacontract.org/2004/07/System.Collections.ObjectModel
664
665
666
667
668 list: The content of the read-only collection; it contains the list of MSOLicenseSuite instances.
61 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 668.1.1.1 RemoteConnectionUserInfo The RemoteConnectionUserInfo type contains user information for a remote connection (see section 2.2.4.26). Namespace: http://contracts.microsoft.com/WindowsServerEssentials/2011/09/WebApi
669
670
671
672
673
674
675
676
AccountName: The account name of the user. FirstName: The first name of the user. LastName: The last name of the user. SidValue: The SID of the user.
676.1.1.1 SearchItemList The SearchItemList type is a collection of metadata from the search results. Namespace: http://contracts.microsoft.com/WindowsServerEssentials/2011/09/WebApi
677
678
679
680
681
682
683
684
685
62 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 UnsearchedShares: A collection of top-level shared folder names that were not successfully searched.
685.1.1.1 ServerInfo The ServerInfo type contains informational data about the server. Namespace: http://contracts.microsoft.com/WindowsServerEssentials/2011/09/WebApi
686
687
688
689
690
691
692
693
694
695
696
697
698
IsMediaStreamingServiceAvailable: A flag that indicates whether the media streaming service is available on the server.
IsTsGatewayEnabled: A flag that indicates whether the TsGateway service is available on the server.
ServerDomainGuid: The globally unique identifier (GUID) of the domain to which the server belongs.
ServerGuid: The GUID of the server.
ServerInternetDomainName: The Internet domain name of the server.
ServerName: The NetBIOS name of the server.
ServerSku: The Product Type of the hosting server.
ServerUtcNow: The current date and time on the server in coordinated universal time (UTC).
ServerVersion: The version of the server.
63 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 698.1.1.1 SharePointSiteAddressCollection The SharePointSiteAddressCollection type contains the SharePoint site address information. Namespace: http://schemas.datacontract.org/2004/07/Microsoft.WindowsServerSolutions.O 365Integration
699
700
701
702
703
704
MySiteAddress: The My Site address. TeamSiteAddress: The SharePoint team site address.
704.1.1.1 StorageDriveInfo The StorageDriveInfo type contains informational data about the drive to be used to create a storage folder (see section 2.2.4.30). Namespace: http://contracts.microsoft.com/WindowsServerEssentials/2011/09/WebApi
705
706
707
708
709
710
711
712
713
714
DeviceName: The name of the device to which the drive belongs.
64 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 FileSystem: The file system of the drive. ShortName: The short name of the drive. Size: The total size of the drive. SizeRemaining: The free space of the drive. VolumeName: The volume name of the drive.
714.1.1.1 StorageServerInfo The StorageServerInfo type contains informational data about the server that can be used to create a storage folder (see section 2.2.4.30). Namespace: http://contracts.microsoft.com/WindowsServerEssentials/2011/09/WebApi
715
716
717
718
719
720
721
722
723
DeviceName: The name of the server.
DfsNameSpace: The DFS namespace of server. This SHOULD be NULL if the server is the second server.
DfsPhysicalPath: The DFS physical path of server. It SHOULD be NULL if the server is the second server.
IsSecondServer: A flag that indicates whether the server is second server.
OperatingSystemName: The name of the operating system of the server.
723.1.1.1 UserInfo The UserInfo type contains informational data about the user. Namespace: http://contracts.microsoft.com/WindowsServerEssentials/2011/09/WebApi
724
725
65 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 726
727
728
729
730
731
732
733
734
735
736
737
738
AccessLevel: The access level for the current user account, which SHOULD be one of the following values: § Unknown § Guest § User § Administrator
CanChangePassword: A flag that indicates whether the user's password can be changed.
FirstName: The first name of the user that is associated with the user account.
Key: The unique key of the user.
LastName: The last name of the user that is associated with the user account.
RemoteWebAccess: A flag that indicates whether the user has remote web access permission.
UserGroups: The list of groups to which the user belongs.
UserGuid: The GUID of the user.
UserName: The name of the user account.
UserStatus: The user status, which SHOULD be one of the following values:
66 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 § Disabled § Enabled § Error
VpnAccess: A flag that indicates whether the user has VPN access permission.
738.1.1.1 WebApiProvider The WebApiProvider type contains informational data about the WebApi provider. Namespace: http://contracts.microsoft.com/WindowsServerEssentials/2011/09/WebApi
739
740
741
742
743
744
745
ContractName: The name of the provider. ContractNameSpace: The namespace of the provider. RelativeLocation: The location of the provider relative to the application root.
745.1.1 Simple Types The following table summarizes the set of common XML schema simple type definitions defined by this specification. Simple Type Description
ContainerType Describes the type of media container. guid Represents a GUID.
MSODomainTypes Indicates the type of the domain for the online services.
MSOLicenseServiceTypes Indicates the type of the license services.
Permission Describes the user access permissions on a folder.
ServerFolderType Describes the server folder type.
ThumbnailFormat A class that specifies the preferred thumbnail image format.
StreamBody A base64 encoded stream of data. char The char simple type represents a Unicode character. duration The duration simple type represents a duration.
67 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 745.1.1.1 ContainerType The ContainerType describes the type of media container.<10> Namespace: http://contracts.microsoft.com/WindowsServerEssentials/2011/09/WebApi
746
747
748
749
750
751
752
753
754
755
756
The following table specifies the allowable values for ContainerType. Value Meaning
Album The type of the media container is "Album".
Artist The type of the media container is "Artist".
Playlist The type of the media container is "Playlist".
Rating The type of the media container is "Rating".
Genre The type of the media container is "Genre".
Folder The type of the media container is "Folder".
Date The type of the media container is "Date".
756.1.1.1 guid This represents a GUID. Namespace: http://schemas.microsoft.com/2003/10/Serialization/
757
758
759
760
761
68 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 761.1.1.1 MSODomainTypes Indicates the type of the domain for the online services. Namespace: http://schemas.datacontract.org/2004/07/Microsoft.WindowsServerSolutions.A zureADObjectModel
762
763
764
765
766
767
768
The following table specifies the allowable values for MSODomainTypes. Value Meaning
None The type of the domain is None.
Email The type of the domain is email.
SharePoint The type of the domain is SharePoint.
768.1.1.1 MSOLicenseServiceTypes Indicates the type of the license services. Namespace: http://schemas.datacontract.org/2004/07/Microsoft.WindowsServerSolutions.A zureADObjectModel
769
770
771
772
773
774
775
776
777
778
69 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 779
780
781
782
The following table specifies the allowable values for MSOLicenseServiceTypes. Value Meaning
None The type of the license service is "None".
Unknown The type of the license service is "Unknown".
ExchangeOnline The type of the license service is "ExchangeOnline".
SharePointOnline The type of the license service is "SharePointOnline".
LyncOnline The type of the license service is "LyncOnline".
IntuneOnline The type of the license service is "IntuneOnline".
782.1.1.1 Permission This class describes the user access permissions on a folder. Namespace: http://schemas.datacontract.org/2004/07/Microsoft.WindowsServerSolutions.S torage
783
784
785
786
787
788
789
790
791
The following table specifies the allowable values for Permission. Value Meaning
None No access permission.
ReadOnly User has read-only permission on the server.
Full User has full permission on the server.
Other User has customized permission on the server.
70 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 Value Meaning
ReadPermissions User has a set of read permissions.
791.1.1.1 ServerFolderType This class describes the server folder type. Namespace: http://schemas.datacontract.org/2004/07/Microsoft.WindowsServerSolutions. WebApi.Management.Storage
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
The following table specifies the allowable values for ServerFolderType. Value Meaning
NonPredefinedType Non-predefined folder type.
MusicType Music folder type.
PicturesType Pictures folder type.
DocumentsType Documents folder type.
VideosType Videos folder type.
BackupsType Backups folder type.
FileBackupsType File backups folder type.
FolderRedirectionType Folder redirection folder type.
CompanyType Company folder type.
71 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 Value Meaning
UserType User folder type.
OtherType System or special use folders type.
806.1.1.1 ThumbnailFormat A class that specifies the preferred thumbnail image format. Namespace: http://contracts.microsoft.com/WindowsServerEssentials/2011/09/WebApi
807
808
809
810
811
812
The following table specifies the allowable values for ThumbnailFormat. Value Meaning
Jpeg The thumbnail that presents as .jpg file.
Png The thumbnail which presents as .png file.
812.1.1.1 StreamBody A base64 encoded stream of data. Namespace: http://schemas.microsoft.com/Message
813
814
815
816
816.1.1.1 char The char simple type represents a Unicode character. Namespace: http://schemas.microsoft.com/2003/10/Serialization
817
818
819
820
72 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 820.1.1.1 duration The duration simple type represents a duration. Namespace: http://schemas.microsoft.com/2003/10/Serialization
821
822
823
824
825
826
827
828
73 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 829 Protocol Details
829.1 SessionService Server Details
829.1.1 Abstract Data Model This section describes a conceptual service contract that an implementation maintains to participate in this protocol. The described operations of the service contract are provided to facilitate the explanation of how the protocol behaves. This document does not mandate that implementations adhere to this service contract as long as their external behavior is consistent with how it is described in this document.
829.1.1.1 SessionId The login call creates a session and generates a SessionId. This SessionId is returned to the client in a response cookie. The logout call ends the session specified by the SessionId in the request cookie.
829.1.1.2 Canary The login call creates a Canary to indicate the user identity; it will be saved on the server. This Canary will be returned to the client in a response header. The logout call disposes of the Canary token and removes it from the server.
829.1.2 Timers None.
829.1.3 Initialization At initialization, the protocol server MUST begin listening for requests at the respective URL addresses given in the message transport (as specified in section 2.1).
829.1.4 Higher-Layer Triggered Events None.
829.1.5 Message Processing Events and Sequencing Rules To call a web service, the client MUST perform these steps: 1. Add the caller's credential in an HTTP header field. The caller's credential is encoded text that is based on the user name and the password. 2. Add Appname (section 2.2.2.1), Apppublisher (section 2.2.2.2), and Appversion (section 2.2.2.3) values in the HTTP header fields. These values are also required to log on. 3. Call the logon method to retrieve the authenticated user token that is issued by the server.
74 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 4. Send subsequent web service requests with the user token in the header. Resource Description
login Generates a valid user token for a valid user.
logout Invalidates the session and user token. The responses to all the operations can result in the following status codes. Status code Reason phrase Description
200 OK Operation successfully completed.
401 Unauthorized Invalid user name or password.
829.1.5.1 login Generates a valid user token for a valid user. HTTP method Description
GET Generates a valid user token for a valid user.
829.1.5.1.1 GET Generates a valid user token for a valid user. This operation is transported by an HTTP GET. The operation can be invoked through the following URI:
830 https://
The request message for this operation contains the following HTTP headers. Request header Usage Value
Authorization The caller's credential is encoded text that is based on user name and password.
AppName The application name.
AppVersion The application version.
AppPublisherName The publisher of the application. The response message for this operation contains the following HTTP header. Response header Usage Value
Canary The user token. The response message for this operation can result in the following status codes. Status code Description
200 Operation successfully completed.
401 Invalid user name or password.
830.1.1.1.1.1Request Body None.
830.1.1.1.1.2Response Body None.
75 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 830.1.1.1.1.3Processing Details 1. The server MUST only respond to requests that have established TLS 1.1 server authentication as specified in [RFC4346]. 2. The client MUST send requests with an authorization header, the value of which starts with "Basic" followed by a blank space and a base64 encoded string of user name and password separated by a colon. 3. The server MUST start a session and generate a user Canary token, as specified in section 2.2.2.5, for the client. 4. The user Canary token MUST be returned to client in Response header.
830.1.1.2 logout Invalidate the session and user token. HTTP method Description
GET Invalidate the session and user token.
830.1.1.2.1 GET Invalidate the session and user token. This operation is transported by an HTTP GET. The operation can be invoked through the following URI:
831 https://
The request message for this operation contains the following HTTP header. Request header Usage Value
Canary The user token. The response message for this operation can result in the following status codes. Status code Description
200 Operation successfully completed.
401 Invalid user token.
831.1.1.1.1.1Request Body None.
831.1.1.1.1.2Response Body None.
831.1.1.1.1.3Processing Details The server MUST only respond to requests that have established TLS 1.1 server authentication [RFC4346]. The user SHOULD log out of the API explicitly when the application exits for security purposes. The server ends the session specified in the request.
76 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 831.1.2 Timer Events None.
831.1.3 Other Local Events None.
831.2 IFileContentAccessService Server Details
831.2.1 Abstract Data Model None.
831.2.2 Timers None.
831.2.3 Initialization At initialization time, the protocol server MUST begin listening for requests at the respective URL addresses given in the message transport (as specified in section 2.1). The storage provider MUST be initialized and configured correctly.
831.2.4 Higher-Layer Triggered Events None.
831.2.5 Message Processing Events and Sequencing Rules
Resource Description filecontent?path={path} The file resource can be downloaded. filecontent?path={path}&overwrite={overwrite} The file resource will be used to upload. itemthumbnail?path={path} The thumbnail of the file item. The responses to all the operations can result in the following status codes. Status Reason code phrase Description
200 OK The operation completed successfully.
400 Bad Request Bad request, the path too long or missing, or the path contains unsupported characters.
401 Unauthorized Access denied to requested resource.
404 Not Found The requested resource does not exist.
201 Created File uploading successfully completed.
409 Conflict Attempted to create a resource that already exists.
831.2.5.1 filecontent?path={path} Retrieves the binary content of a file in bytes. path: This is the description of the parameter path.
77 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 HTTP method Description
GET Retrieves the binary content of a file in bytes.
831.2.5.1.1 GET This API retrieves the binary content of a file in bytes. The caller reads the response stream. The API supports retrieving partial content of the file range that is specified by the Range header in an HTTP request. This operation is transported by an HTTP GET. The operation can be invoked through the following URI:
832 https://
The request message for this operation contains the following HTTP headers. Request header Usage Value
Range Optional Request only part of an entity, as specified in section 2.2.2.7.
Canary Optional The user token, as specified in section 2.2.2.5. Client MUST either pass this header to server or pass all of the following headers to the server.
Authorization Optional The caller's credentials, which are encoded text that is based on the user name and password as specified in section 2.2.2.4.
AppName Optional The client application name, as specified in section 2.2.2.1.
AppVersion Optional The client application version, as specified in section 2.2.2.3.
AppPublisherName Optional The client application publisher name, as specified in section 2.2.2.2. The response message for this operation can result in one of the following status codes. Status code Description
200 Download operation successfully completed.
400 Input parameters are invalid.
401 User is not allowed to access resource.
404 Requested resource does not exist.
832.1.1.1.1.1Request Body None.
832.1.1.1.1.2Response Body The response body is encoded in the following XML format.
833
833.1.1.1.1.1Processing Details This operation downloads a file in the form of a file stream from the location specified by the path.
78 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 833.1.1.2 filecontent?path={path}&overwrite={overwrite} Uploads a file to a location for which the user has access permissions. path: The path of the file. overwrite: This flag indicates whether to overwrite the file if it exists on server. See section 2.2.3.30. HTTP method Description
POST Uploads a file to a location where the user has access permissions.
833.1.1.2.1 POST The file content SHOULD be put into the HTTP request. The protocol does not support resuming uploads. By default, the maximum size of a file that can be uploaded is 100 MB. This operation is transported by an HTTP POST. The operation can be invoked through the following URI:
834 https://
The request message for this operation contains the following HTTP headers. Request header Usage Value
Canary Optional The value returned in the logon Response Canary header. The client MUST either pass this header to the server or pass all of the following headers to the client. For more details, refer to section 2.2.2.5.
Authorization Optional The caller's credential is encoded text that is based on a user name and password. For more details, refer to section 2.2.2.4.
AppName Optional The application name, as specified in section 2.2.2.1.
AppVersion Optional The application version, as specified in section 2.2.2.3.
AppPublisherName Optional The application publisher name, as specified in section 2.2.2.2. The response message for this operation can result in one of the following status codes. Status code Description
201 File uploading successfully completed.
401 User is not allowed to access resource.
404 The specific resource does not exist.
409 An item already exists with the requested new name.
834.1.1.1.1.1Request Body The request body is a binary stream.
834.1.1.1.1.2Response Body None.
834.1.1.1.1.3Processing Details This operation uploads a file to the location specified by the path.
79 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 834.1.1.2 itemthumbnail?path={path} Retrieves a thumbnail of a single item. path: HTTP method Description
GET Retrieves a thumbnail of a single item.
834.1.1.2.1 GET Retrieves a thumbnail of a single item. This method supports most image formats. This operation is transported by an HTTP GET. The operation can be invoked through the following URI:
835 https://
The request message for this operation contains the following HTTP headers. Request header Usage Value
Canary Optional The value returned in logon Response canary header. Client MUST either pass this header to server or pass all of the following headers to the client. For more details, see section 2.2.2.5.
Authorization Optional The caller's credential is encoded text that is based on user name and password. For more details, see section 2.2.2.4.
AppName Optional The application name. For more details, see section 2.2.2.1.
AppVersion Optional The application version. For more details, see section 2.2.2.3.
AppPublisherName Optional The application publisher name. For more details, see section 2.2.2.2. The response message for this operation can result in the following status codes. Status code Description
200 Operation successfully completed.
400 One or more parameters are not valid.
401 Access to the requested resource is denied.
404 The path does not exist.
835.1.1.1.1.1Request Body None.
835.1.1.1.1.2Response Body The response body is encoded in either XML format or JSON format. The format is controlled by the Accept header defined in section 2.2.2.6. For the detailed definition of response body, refer to section 2.2.4.34.
836
836.1.1.1.1.1Processing Details
80 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 This call will return the item thumbnail to the client. The server MUST construct a response in either XML or JSON format based on the value of the Accept header (section 2.2.2.6), or in XML format if the Accept header is not present. The response MUST include all of the complex types defined in section 2.2.4.34.
836.1.2 Timer Events None.
836.1.3 Other Local Events None.
836.2 IFileOperationService Server Details
836.2.1 Abstract Data Model None.
836.2.2 Timers None.
836.2.3 Initialization At initialization time, the protocol server MUST begin listening for requests at the respective URL addresses given in the message transport (as specified in section 2.1). The storage provider MUST be initialized and configured correctly.
836.2.4 Higher-Layer Triggered Events None.
836.2.5 Message Processing Events and Sequencing Rules
Descript Resource ion items/index/{index}/count/{count}? ItemList path={path}&filter={filter}&sortbyfield={sortbyfield}&ascending={ascending} object that represen ts a collection of file items in the specified folder. items/index/{index}/count/{count}/search? SearchIt query={query}&sortbyfield={sortbyfield}&ascending={ascending}&scope={scope}&timeoutseconds emList ={timeoutseconds} object that represen ts a collection
81 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 Descript Resource ion
of file items that match the specified keyword. folder/newsubfoldername?path={path}&language={language} Default available new folder name in specified language . itemmetadata?path={path} ItemInfo object that represen ts the specified file item. folder?path={path} Folder being created. item/rename?path={path}&newname={newname} File being renamed . item/delete?path={path} File item being deleted. accessuri?path={path} Tempora ry URI that can be used to downloa d a file. item/move?newpath={newpath}&originalpath={originalpath} File item being moved from another location. item/copy?newpath={newpath}&originalpath={originalpath} File item being copied from another location. The responses to all the operations can result in the following status codes. Status code Reason phrase Description
200 OK The operation successfully completed.
400 Bad Request One or more parameters are not valid.
401 Unauthorized Access to the requested resource is denied.
82 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 Status code Reason phrase Description
404 Not Found The path does not exist.
501 Not Implemented The server does not have the functionality to support the requested operation.
503 Service The server is currently unable to handle the request. Unavailable
504 Gateway Timeout The request does not finish within a given time interval.
201 Created The request resource is created.
409 Conflict The request fails due to a conflict with the current resource.
836.2.5.1 items/index/{index}/count/{count}? path={path}&filter={filter}&sortbyfield={sortbyfield}&ascending={ascending } The URI is an ItemList object that represents a collection of file items within the specified folder. index: The numerical position of the first item to be retrieved (see section 2.2.3.18). count: The number of items to be retrieved (see section 2.2.3.5). path: The UNC path of the folder (see section 2.2.3.32). filter: The type of files to be retrieved (see section 2.2.3.11). All file types will be retrieved if this parameter is ignored. sortbyfield: The field of the file item property by which file items are sorted (see section 2.2.3.42). ascending: A Boolean value that indicates whether the sorting is ascending (see section 2.2.3.3). Ascending sorting is performed if this parameter is ignored. HTTP method Description
GET Retrieves the metadata information of items in a folder.
836.2.5.1.1 GET The GET method retrieves the metadata information of items under a folder. The metadata includes basic information such as the creation time, item type, modification time, name, path, and size. This operation is transported by an HTTP GET. The operation can be invoked through the following URI:
837 https://
The request message for this operation contains the following HTTP headers. Request header Usage Value
Canary Optional The value returned in the logon Response Canary header. The client MUST either pass this header to the server or pass all of following headers to the client. For more details, see section 2.2.2.5.
83 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 Request header Usage Value
Authorization Optional The caller's credential is encoded text that is based on user name and password. For more details, see section 2.2.2.4.
AppName Optional The application name. For more details, see section 2.2.2.1.
AppVersion Optional The application version. For more details, see section 2.2.2.3.
AppPublisherName Optional The name of the application publisher. For more details, see section 2.2.2.2. The response message for this operation can result in the following status codes. Status code Description
200 The operation successfully completed.
400 One or more parameters are not valid.
401 Access to the requested resource is denied.
404 The path does not exist.
837.1.1.1.1.1Request Body None.
837.1.1.1.1.2Response Body The response body is encoded in XML or JSON format according to the ACCEPT header of the request.
838
838.1.1.1.1.1Processing Details This operation enumerates the file items in the specified folder and returns a collection of metadata that fulfils the specified parameters.
838.1.1.2 items/index/{index}/count/{count}/search? query={query}&sortbyfield={sortbyfield}&ascending={ascending}&scope={sc ope}&timeoutseconds={timeoutseconds} This URI represents a search method that returns a SearchItemList object. The SearchItemList object represents a collection of file items that match the specified keyword. index: The numerical position of the first item to be retrieved (see section 2.2.3.18). count: The number of items to be retrieved (see section 2.2.3.5). query: The start string to search for within the names of the files and folders. The asterisk (*) and question mark (?) wildcard characters are supported (see section 2.2.3.34). sortbyfield: The field of the file item property by which file items are sorted (see section 2.2.3.42). ascending: A Boolean value that indicates whether the sorting is ascending (see section 2.2.3.3). If this parameter is ignored, ascending sorting is applied. scope: The UNC path of the folder where the search is performed (see section 2.2.3.37). All shared folders are searched if this parameter is ignored.
84 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 timeoutseconds: The number of seconds after which the request times out (see section 2.2.3.47). Timeout interval is set to 10 seconds if this parameter is ignored.
HTTP method Description
GET Retrieves the metadata information for search results.
838.1.1.2.1 GET The GET method retrieves the metadata information for search results. The metadata includes basic information such as the creation time, item type, modification time, name, path, and size. The search occurs across all share folders that users have access to. This operation is transported by an HTTP GET. The operation can be invoked through the following URI:
839 https://
The request message for this operation contains the following HTTP headers. Request header Usage Value
Canary Optional The value returned in login Response Canary header. Client MUST either pass this header to the server or pass all of the following headers to the client. For more details, see section 2.2.2.5.
Authorization Optional The caller's credential is encoded text that is based on user name and password. For more details, see section 2.2.2.4.
AppName Optional Application name. For more details, see section 2.2.2.1.
AppVersion Optional Application version. For more details, see section 2.2.2.3.
AppPublisherName Optional Application publisher name. For more details, see section 2.2.2.2. The response message for this operation can result in the following status codes. Status code Description
200 Operation successfully completed.
400 One or more parameters are not valid.
401 Access to the requested resource is denied.
501 Windows search service is not available.
503 Windows search service failed to perform the search.
504 Search does not finish within the specified timeout interval.
839.1.1.1.1.1Request Body None.
839.1.1.1.1.2Response Body The response body is encoded in XML or JSON format according to the ACCEPT header of the request.
85 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 840
840.1.1.1.1.1Processing Details This operation searches file items in the specified folder and returns the collection of metadata that fulfills the specified parameters.
840.1.1.2 folder/newsubfoldername?path={path}&language={language} This URI represents the unique name to use for a new folder. path: The UNC path (specified in section 2.2.3.32) for the new folder. language: The language/region code (such as en-us) (specified in section 2.2.3.21) of the new folder.
HTTP method Description
GET Generates an unused name to use for a new folder.
840.1.1.2.1 GET The GET operation generates a unique name to use for a new folder. This operation is transported by an HTTP GET. The operation can be invoked through the following URI:
841 https://
The request message for this operation contains the following HTTP headers. Request header Usage Value
Canary Optional The value returned in the logon Response Canary header. Client MUST either pass this header to the server or pass all of the following headers to the client. For more details, see section 2.2.2.5.
Authorization Optional The caller's credential is encoded text that is based on user name and password. For more details, see section 2.2.2.4.
AppName Optional Application name. For more details, see section 2.2.2.1.
AppVersion Optional Application version. For more details, see section 2.2.2.3.
AppPublisherName Optional Application publisher name. For more details, see section 2.2.2.2. The response message for this operation can result in the following status codes. Status code Description
200 Operation successfully completed.
400 One or more parameters are not valid.
401 Access to the requested resource is denied.
404 Folder specified by the path does not exist.
841.1.1.1.1.1Request Body None.
86 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 841.1.1.1.1.2Response Body The response body is encoded in XML or JSON format according to the ACCEPT header of the request.
842
842.1.1.1.1.1Processing Details This operation retrieves the next available new folder name with the predefined pattern in the specified folder.
842.1.1.2 itemmetadata?path={path} This URI represents the basic metadata of a single item. path: The UNC path (section 2.2.3.32) of the file item.
HTTP method Description
GET Retrieves the basic metadata of a single item.
842.1.1.2.1 GET The GET operation retrieves the basic metadata of a single item. This operation is transported by an HTTP GET. The operation can be invoked through the following URI:
843 https://
The request message for this operation contains the following HTTP headers. Request header Usage Value
Canary Optional The value returned in the logon Response Canary header. Client MUST either pass this header to the server or pass all of the following headers to the client. For more details, see section 2.2.2.5.
Authorization Optional The caller's credential is encoded text that is based on user name and password. For more details, see section 2.2.2.4.
AppName Optional Application name. For more details, see section 2.2.2.1.
AppVersion Optional Application version. For more details, see section 2.2.2.3.
AppPublisherName Optional Application publisher name. For more details, see section 2.2.2.2. The response message for this operation can result in the following status codes. Status code Description
200 Operation successfully completed.
400 One or more parameters are not valid.
401 Access to the requested resource is denied.
404 The path does not exist.
843.1.1.1.1.1Request Body
87 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 None.
843.1.1.1.1.2Response Body The response body is encoded in XML or JSON format according to ACCEPT header of the request.
844
844.1.1.1.1.1Processing Details This operation returns the metadata of the specified file item.
844.1.1.2 folder?path={path} This URI represents a new folder in a path where the user has the required permissions. path:The UNC path (section 2.2.3.32) of the new folder.
HTTP method Description
POST Creates a new folder in a path where the user has the required permissions.
844.1.1.2.1 POST The POST operation creates a new folder in a path where the user has the required permissions. This operation is transported by an HTTP POST. The operation can be invoked through the following URI:
845 https://
The request message for this operation contains the following HTTP headers. Request header Usage Value
Canary Optional The value returned in the logon Response Canary header. Client MUST either pass this header to the server or pass all of the following headers to the client. For more details, see section 2.2.2.5.
Authorization Optional The caller's credential is encoded text that is based on user name and password. For more details, see section 2.2.2.4.
AppName Optional Application name. For more details, see section 2.2.2.1.
AppVersion Optional Application version. For more details, see section 2.2.2.3.
AppPublisherName Optional Application publisher name. For more details, see section 2.2.2.2. The response message for this operation can result in the following status codes. Status code Description
201 The folder is created.
400 One or more parameters are not valid.
401 Access to the requested resource is denied.
409 File item with the new name exists.
88 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 845.1.1.1.1.1Request Body None.
845.1.1.1.1.2Response Body The response body is encoded in XML or JSON format according to the ACCEPT header of the request.
845.1.1.1.1.3Processing Details This operation creates a new folder with the given name in the specified folder.
845.1.1.2 item/rename?path={path}&newname={newname} This URI represents the name of an existing item. path: UNC path of the file item to be renamed (see section 2.2.3.32). newname: The new name of the item (see section 2.2.3.26).
HTTP method Description
POST Changes the name of an existing item.
845.1.1.2.1 POST The POST operation changes the name of an existing item. This operation is transported by an HTTP POST. The operation can be invoked through the following URI:
846 https://
The request message for this operation contains the following HTTP headers. Request header Usage Value
Canary Optional The value returned in the logon Response Canary header. Client MUST either pass this header to the server or pass all of the following headers to the server. For more details, see section 2.2.2.5.
Authorization Optional The caller's credential is encoded text that is based on user name and password. For more details, see section 2.2.2.4.
AppName Optional Application name. For more details, see section 2.2.2.1.
AppVersion Optional Application version. For more details, see section 2.2.2.3.
AppPublisherName Optional Application publisher name. For more details, see section 2.2.2.2. The response message for this operation can result in the following status codes. Status code Description
200 Operation successfully completed.
400 One or more parameters are not valid.
401 Access to the requested resource is denied.
404 The path does not exist.
409 File item with the new name exists.
89 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 846.1.1.1.1.1Request Body None.
846.1.1.1.1.2Response Body None.
846.1.1.1.1.3Processing Details This operation changes name of the specified file item.
846.1.1.2 item/delete?path={path} This URI represents an existing item in a path where the user has the required permissions to delete. path: UNC path of the file to be deleted (see section 2.2.3.32).
HTTP method Description
POST Deletes an existing item in a path where the user has the required permissions. If the path is a folder, the method also removes all items in the folder.
846.1.1.2.1 POST The POST method deletes an existing item in a path where the user has the required permissions. If the path is a folder, the method also removes all items in the folder. This operation is transported by an HTTP POST. The operation can be invoked through the following URI:
847 https://
The request message for this operation contains the following HTTP headers. Request header Usage Value
Canary Optional The value returned in the logon Response Canary header. Client MUST either pass this header to the server or pass all of the following headers to the server. For more details, see section 2.2.2.5.
Authorization Optional The caller's credential is encoded text that is based on user name and password. For more details, see section 2.2.2.4.
AppName Optional Application name. For more details, see section 2.2.2.1.
AppVersion Optional Application version. For more details, see section 2.2.2.3.
AppPublisherName Optional Application publisher name. For more details, see section 2.2.2.2.
847.1.1.1.1.1Request Body None.
90 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 847.1.1.1.1.2Response Body None.
847.1.1.1.1.3Processing Details This operation deletes the specified file item.
847.1.1.2 accessuri?path={path} This URI represents a temporary URL for a file. path: The UNC path of the file (see section 2.2.3.32).
HTTP method Description
GET Retrieves a temporary URL for a file.
847.1.1.2.1 GET The GET method retrieves a temporary URL for a file. The URL can be accessed only twice and only within 30 seconds after retrieval. This operation is transported by an HTTP GET. The operation can be invoked through the following URI:
848 https://
The request message for this operation contains the following HTTP headers. Request header Usage Value
Canary Optional The value returned in the logon Response Canary header. Client MUST either pass this header to the server or pass all of the following headers to the server. For more details, see section 2.2.2.5.
Authorization Optional The caller's credential is encoded text that is based on user name and password. For more details, see section 2.2.2.4.
AppName Optional Application name. For more details, see section 2.2.2.1.
AppVersion Optional Application version. For more details, see section 2.2.2.3.
AppPublisherName Optional Application publisher name. For more details, see section 2.2.2.2. The response message for this operation can result in the following status codes. Status code Description
200 Operation successfully completed.
400 One or more parameters are not valid.
401 Access to the requested resource is denied.
404 The path does not exist.
848.1.1.1.1.1Request Body None.
848.1.1.1.1.2Response Body
91 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 The response body is encoded in XML or JSON format according to the ACCEPT header of the request.
849
849.1.1.1.1.1Processing Details This operation retrieves a temporary URL for a file. The URL can be accessed only twice and only within 30 seconds after retrieval.
849.1.1.2 item/move?newpath={newpath}&originalpath={originalpath} This URI represents a file item that can be moved to another location. originalpath: UNC path of the file item (see section 2.2.3.29). newpath: The new UNC path of the file item (see section 2.2.3.27).
HTTP method Description
POST Move a file item to another location.
849.1.1.2.1 POST The POST method moves a file item to another location. This operation is transported by an HTTP POST. The operation can be invoked through the following URI:
850 https://
The request message for this operation contains the following HTTP headers. Request header Usage Value
Canary Optional The value returned in the logon Response Canary header. Client MUST either pass this header to the server or pass all of the following headers to the server. For more details, see section 2.2.2.5.
Authorization Optional The caller's credential is encoded text that is based on user name and password. For more details, see section 2.2.2.4.
AppName Optional Application name. For more details, see section 2.2.2.1.
AppVersion Optional Application version. For more details, see section 2.2.2.3.
AppPublisherName Optional Application publisher name. For more details, see section 2.2.2.2. The response message for this operation can result in the following status codes. Status code Description
200 Operation successfully completed.
400 One or more parameters are not valid.
401 Access to the requested resource is denied.
404 The path does not exist.
409 File item with the new path exists.
92 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 850.1.1.1.1.1Request Body None.
850.1.1.1.1.2Response Body None.
850.1.1.1.1.3Processing Details This operation moves a file item to another location.
850.1.1.2 item/copy?newpath={newpath}&originalpath={originalpath} This URI represents a file item that can be copied to another location. originalpath: UNC path of the file item (see section 2.2.3.29). newpath: The new UNC path of the file item (see section 2.2.3.27).
HTTP method Description
POST Copy a file item to another location.
850.1.1.2.1 POST The POST method copies a file item to another location. This operation is transported by an HTTP POST. The operation can be invoked through the following URI:
851 https://
The request message for this operation contains the following HTTP headers. Request header Usage Value
Canary Optional The value returned in the logon Response Canary header. Client MUST either pass this header to the server or pass all of the following headers to the server. For more details, see section 2.2.2.5.
Authorization Optional The caller's credential is encoded text that is based on user name and password. For more details, see section 2.2.2.4.
AppName Optional Application name. For more details, see section 2.2.2.1.
AppVersion Optional Application version. For more details, see section 2.2.2.3.
AppPublisherName Optional Application publisher name. For more details, see section 2.2.2.2. The response message for this operation can result in the following status codes. Status code Description
200 Operation successfully completed.
400 One or more parameters are not valid.
401 Access to the requested resource is denied.
404 The path does not exist.
409 File item with the new path has existed.
93 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 851.1.1.1.1.1Request Body None.
851.1.1.1.1.2Response Body None.
851.1.1.1.1.3Processing Details This operation copies the file item to another location.
851.1.2 Timer Events None.
851.1.3 Other Local Events None.
851.2 IAzureADManagement Server Details
851.2.1 Abstract Data Model This section describes a conceptual service contract that an implementation maintains in order to participate in this protocol. The described operations of the service contract are provided to facilitate the explanation of how the protocol behaves. This document does not mandate that implementations adhere to this service contract as long as their external behavior is consistent with how it is described in this document.
851.2.1.1 MSOUser The data model uses the full complex types defined in section 2.2.4.53.
851.2.1.2 MSOTenantInformation The data model uses the full complex types defined in section 2.2.4.52.
851.2.1.3 ArrayOfMSODomain The data model uses the full complex types defined in section 2.2.4.13.
851.2.2 Timers None.
851.2.3 Initialization None.
851.2.4 Higher-Layer Triggered Events None.
94 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 851.2.5 Message Processing Events and Sequencing Rules
Resource Description msouser?localusername={localusername} Get the mapped Microsoft online user's information. msousers Get all Microsoft online users. msouser/create?localusername={localusername}&onlineusername={onlineusername} Create a Microsoft online user. msouser/assign?localusername={localusername}&onlineusername={onlineusername} Assign a Microsoft online user to local user. msouser/unassign?localusername={localusername} Un-assign the Microsoft online user from local user. msouser/enable?localusername={localusername} Enable the Microsoft online user. msouser/disable?localusername={localusername} Disable the Microsoft online user. msouser/delete?localusername={localusername} Delete the Microsoft online user. msodomains Get all accepted Microsoft online domains. msosubscriptioninfo Get Microsoft online subscription information. msolicense/set?localusername={localusername} Set Microsoft online account license. The responses to all the operations can result in the following status codes. Status code Reason phrase Description
200 OK The operation successfully completed.
400 Bad Request Invalid parameter.
401 Unauthorized The user is not authorized for web access.
404 Not Found Cannot find the local user or online user.
500 Internal server error An internal server error occurred.
409 Conflict The operation failed because of the status conflict.
501 Not Implemented The operation is not supported.
403 Forbidden The operation is forbidden.
851.2.5.1 msouser?localusername={localusername} Retrieves the mapped online user. localusername: Local user name.
HTTP method Description
GET Retrieve the mapped online user.
95 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 851.2.5.1.1 GET This API retrieves the online user mapped to the local user. This operation is transported by an HTTP GET. The operation can be invoked through the following URI:
852 https://
The request message for this operation contains the following HTTP headers. Request header Usage Value
Canary Optional The user token. Client MUST either pass this header to the server or pass all of the following headers to the server. For more details, refer to section 2.2.2.5.
Authorization Optional The caller's credential is encoded text that is based on user name and password. For more details, refer to section 2.2.2.4.
AppName Optional The client application name. For more details, refer to section 2.2.2.1.
AppVersion Optional The client application version. For more details, refer to section 2.2.2.3.
AppPublisherName Optional The client application publisher name. For more details, refer to section 2.2.2.2. The response message for this operation can result in the following status codes. Status code Description
200 Operation successfully completed.
400 Invalid parameter.
401 The user is not authorized for web access.
404 Cannot find the local user or online user.
500 Internal server error.
852.1.1.1.1.1Request Body None.
852.1.1.1.1.2Response Body The response body is encoded in either XML or JSON format. The format is controlled by the Accept header specified in section 2.2.4.53.
853
853.1.1.1.1.1Processing Details This call returns the information of the online user. See section 2.2.4.53. The server MUST construct a response in either XML or JSON format based on the value of the Accept header (section 2.2.2.6), or in XML format if the Accept header is not present.
853.1.1.2 msousers Retrieves all of the online users.
96 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 HTTP method Description
GET Retrieves all of the online users.
853.1.1.2.1 GET This API retrieves all of the online users. This operation is transported by an HTTP GET. The operation can be invoked through the following URI:
854 https://
The request message for this operation contains the following HTTP headers. Request header Usage Value
Canary Optional The user token. Client MUST either pass this header to the server or pass all of the following headers to the server. For more details, refer to section 2.2.2.5.
Authorization Optional The caller's credential is encoded text that is based on user name and password. For more details, refer to section 2.2.2.4.
AppName Optional The client application name. For more details, refer to section 2.2.2.1.
AppVersion Optional The client application version. For more details, refer to section 2.2.2.3.
AppPublisherName Optional The client application publisher name. For more details, refer to section 2.2.2.2. The response message for this operation can result in the following status codes. Status code Description
200 Operation successfully completed.
400 Invalid parameter.
401 The user is not authorized for web access.
500 Internal server error.
854.1.1.1.1.1Request Body None.
854.1.1.1.1.2Response Body The response body is encoded in either XML or JSON format. The format is controlled by the Accept header defined in section 2.2.4.18.
855
855.1.1.1.1.1Processing Details This call returns the information of all the online users. See section 2.2.4.18. The server MUST construct a response in either XML or JSON format based on the value of the Accept header (section 2.2.2.6), or in XML format if the Accept header is not present.
97 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 855.1.1.2 msouser/create? localusername={localusername}&onlineusername={onlineusername} Creates an online user and assigns to the local user. localusername: Local user name. onlineusername: Online user name, recommended to be a UPN.
HTTP method Description
POST Create an online user and assign to the local user.
855.1.1.2.1 POST This API creates an online user and assigns to the local user. This operation is transported by an HTTP POST. The operation can be invoked through the following URI:
856 https://
The request message for this operation contains the following HTTP headers. Request header Usage Value
Canary Optional The value returned in the logon Response Canary header. Client MUST either pass this header to the server or pass all of the following headers to the server. For more details, refer to section 2.2.2.5.
Authorization Optional The caller's credential is encoded text that is based on user name and password. For more details, refer to section 2.2.2.4.
AppName Optional Application name. For more details, refer to section 2.2.2.1.
AppVersion Optional Application version. For more details, refer to section 2.2.2.3.
AppPublisherName Optional Application publisher name. For more details, refer to section 2.2.2.2. The response message for this operation can result in the following status codes. Status code Description
200 Operation successfully completed.
400 Invalid parameter.
401 The user is not authorized for web access.
404 Cannot find the local user or online user.
409 Operation failed because of the status conflict.
500 Internal server error.
856.1.1.1.1.1Request Body The request body is encoded in XML format or JSON format based on the value of the Accept header (section 2.2.2.6), or in XML format if the Accept header is not present.
856.1.1.1.1.2Response Body
98 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 None.
856.1.1.1.1.3Processing Details This API creates an online user and assigns to the local user.
856.1.1.2 msouser/assign? localusername={localusername}&onlineusername={onlineusername} This API assigns the online user to the local user. localusername: Local user name. onlineusername: Online user name.
HTTP method Description
POST This API will assign the online user to the local user.
856.1.1.2.1 POST This API assigns the online user to the local user. This operation is transported by an HTTP POST. The operation can be invoked through the following URI:
857 https://
The request message for this operation contains the following HTTP headers. Request header Usage Value
Canary Optional The value returned in the logon Response Canary header. Client MUST either pass this header to the server or pass all of the following headers to the server. For more details, refer to section 2.2.2.5.
Authorization Optional The caller's credential is encoded text that is based on user name and password. For more details, refer to section 2.2.2.4.
AppName Optional Application name. For more details, refer to section 2.2.2.1.
AppVersion Optional Application version. For more details, refer to section 2.2.2.3.
AppPublisherName Optional Application publisher name. For more details, refer to section 2.2.2.2. The response message for this operation can result in the following status codes. Status code Description
200 Operation successfully completed.
400 Invalid parameter.
401 The user is not authorized for web access.
404 Cannot find the local user or online user.
409 Operation failed because of the status conflict.
500 Internal server error.
501 Operation is not supported.
99 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 857.1.1.1.1.1Request Body None.
857.1.1.1.1.2Response Body None.
857.1.1.1.1.3Processing Details This API reassigns the online user to the local user.
857.1.1.2 msouser/unassign?localusername={localusername} This API reassigns the online user to the local user. localusername:
HTTP method Description
POST This API reassigns the online user to the local user.
857.1.1.2.1 POST This API reassigns the online user to the local user. This operation is transported by an HTTP POST. The operation can be invoked through the following URI:
858 https://
The request message for this operation contains the following HTTP headers. Request header Usage Value
Canary Optional The value returned in the logon Response Canary header. Client MUST either pass this header to the server or pass all of the following headers to the server. For more details, refer to section 2.2.2.5.
Authorization Optional The caller's credential is encoded text that is based on user name and password. For more details, refer to section 2.2.2.4.
AppName Optional Application name. For more details, refer to section 2.2.2.1.
AppVersion Optional Application version. For more details, refer to section 2.2.2.3.
AppPublisherName Optional Application publisher name. For more details, refer to section 2.2.2.2. The response message for this operation can result in the following status codes. Status code Description
200 Operation successfully completed.
400 Invalid parameter.
401 The user is not authorized for web access.
404 Cannot find the local user or online user.
409 Operation failed because of the status conflict.
500 Internal server error.
501 Operation is not supported.
100 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 858.1.1.1.1.1Request Body None.
858.1.1.1.1.2Response Body None.
858.1.1.1.1.3Processing Details This API reassigns the online user to the local user.
858.1.1.2 msouser/enable?localusername={localusername} This API enables the online user, which is mapped to the local user. localusername:local user name
HTTP method Description
POST This API enables the online user, which is mapped to the local user.
858.1.1.2.1 POST This API enables the online user, which is mapped to the local user. This operation is transported by an HTTP POST. The operation can be invoked through the following URI:
859 https://
The request message for this operation contains the following HTTP headers. Request header Usage Value
Canary Optional The value returned in the logon Response Canary header. Client MUST either pass this header to the server or pass all of the following headers to the server. For more details, refer to section 2.2.2.5.
Authorization Optional The caller's credential is encoded text that is based on user name and password. For more details, refer to section 2.2.2.4.
AppName Optional Application name. For more details, refer to section 2.2.2.1.
AppVersion Optional Application version. For more details, refer to section 2.2.2.3.
AppPublisherName Optional Application publisher name. For more details, refer to section 2.2.2.2. The response message for this operation can result in the following status codes. Status code Description
200 Operation successfully completed.
400 Invalid parameter.
401 The user is not authorized for web access.
404 Cannot find the local user or online user.
500 Internal server error.
501 Operation is not supported.
101 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 Status code Description
859.1.1.1.1.1Request Body None.
859.1.1.1.1.2Response Body None.
859.1.1.1.1.3Processing Details This API enables the online user, which is mapped to the local user.
859.1.1.2 msouser/disable?localusername={localusername} This API disables the online user, which is mapped to the local user. localusername: Local user name.
HTTP method Description
POST This API disables the online user, which is mapped to the local user.
859.1.1.2.1 POST This API disables the online user, which is mapped to the local user. This operation is transported by an HTTP POST. The operation can be invoked through the following URI:
860 https://
The request message for this operation contains the following HTTP headers. Request header Usage Value
Canary Optional The value returned in the logon Response Canary header. Client MUST either pass this header to the server or pass all of the following headers to the server. For more details, refer to section 2.2.2.5.
Authorization Optional The caller's credential is encoded text that is based on user name and password. For more details, refer to section 2.2.2.4.
AppName Optional Application name. For more details, refer to section 2.2.2.1.
AppVersion Optional Application version. For more details, refer to section 2.2.2.3.
AppPublisherName Optional Application publisher name. For more details, refer to section 2.2.2.2. The response message for this operation can result in the following status codes. Status code Description
200 Operation successfully completed.
400 Invalid parameter.
401 The user is not authorized for web access.
403 Operation is forbidden.
102 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 Status code Description
404 Cannot find the local user or online user.
500 Internal server error.
501 Operation is not supported.
860.1.1.1.1.1Request Body None.
860.1.1.1.1.2Response Body None.
860.1.1.1.1.3Processing Details This API disables the online user, which is mapped to the local user.
860.1.1.2 msouser/delete?localusername={localusername} This API deletes the online user, which is mapped to the local user. localusername:
HTTP method Description
POST This API deletes the online user, which is mapped to the local user.
860.1.1.2.1 POST This API deletes the online user, which is mapped to the local user. This operation is transported by an HTTP POST. The operation can be invoked through the following URI:
861 https://
The request message for this operation contains the following HTTP headers. Request header Usage Value
Canary Optional The value returned in the logon Response Canary header. Client MUST either pass this header to the server or pass all of the following headers to the server. For more details, refer to section 2.2.2.5.
Authorization Optional The caller's credential is encoded text that is based on user name and password. For more details, refer to section 2.2.2.4.
AppName Optional Application name. For more details, refer to section 2.2.2.1.
AppVersion Optional Application version. For more details, refer to section 2.2.2.3.
AppPublisherName Optional Application publisher name. For more details, refer to section 2.2.2.2. The response message for this operation can result in the following status codes. Status code Description
200 Operation successfully completed.
103 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 Status code Description
400 Invalid parameter.
401 The user is not authorized for web access.
403 Operation is forbidden.
404 Cannot find the local user or online user.
500 Internal server error.
861.1.1.1.1.1Request Body None.
861.1.1.1.1.2Response Body None.
861.1.1.1.1.3Processing Details This API deletes the online user, which is mapped to the local user.
861.1.1.2 msodomains This API retrieves all the accepted online domains. HTTP method Description
GET This API retrieves all the accepted online domains.
861.1.1.2.1 GET This API retrieves all the accepted online domains. This operation is transported by an HTTP GET. The operation can be invoked through the following URI:
862 https://
The request message for this operation contains the following HTTP headers. Request header Usage Value
Canary Optional The value returned in the logon Response Canary header. Client MUST either pass this header to the server or pass all of the following headers to the server. For more details, refer to section 2.2.2.5.
Authorization Optional The caller's credential is encoded text that is based on user name and password. For more details, refer to section 2.2.2.4.
AppName Optional Application name. For more details, refer to section 2.2.2.1.
AppVersion Optional Application version. For more details, refer to section 2.2.2.3.
AppPublisherName Optional Application publisher name. For more details, refer to section 2.2.2.2. The response message for this operation can result in the following status codes. Status code Description
200 Operation successfully completed.
104 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 Status code Description
400 Invalid parameter.
401 The user is not authorized for web access.
500 Internal server error.
862.1.1.1.1.1Request Body None.
862.1.1.1.1.2Response Body The response body is encoded in either XML or JSON format. The format is controlled by the Accept header defined in section 2.2.4.13.
863
863.1.1.1.1.1Processing Details This call returns the information of the accepted online domains. See section 2.2.4.13. The server MUST construct a response in either XML or JSON format based on the value of the Accept header (section 2.2.2.6), or in XML format if the Accept header is not present.
863.1.1.2 msosubscriptioninfo This API retrieves the online subscription information. HTTP method Description
GET This API retrieves the online subscription information.
863.1.1.2.1 GET This API retrieves the online subscription information. This operation is transported by an HTTP GET. The operation can be invoked through the following URI:
864 https://
The request message for this operation contains the following HTTP headers. Request header Usage Value
Canary Optional The value returned in the logon Response Canary header. Client MUST either pass this header to the server or pass all of the following headers to the server. For more details, refer to section 2.2.2.5.
Authorization Optional The caller's credential is encoded text that is based on user name and password. For more details, refer to section 2.2.2.4.
AppName Optional Application name. For more details, refer to section 2.2.2.1.
AppVersion Optional Application version. For more details, refer to section 2.2.2.3.
AppPublisherName Optional Application publisher name. For more details, refer to section 2.2.2.2.
105 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 The response message for this operation can result in the following status codes. Status code Description
200 Operation successfully completed.
400 Invalid parameter.
401 The user is not authorized for web access.
500 Internal server error.
864.1.1.1.1.1Request Body None.
864.1.1.1.1.2Response Body The response body is encoded in either XML or JSON format. The format is controlled by the Accept header defined in section 2.2.4.52.
865
865.1.1.1.1.1Processing Details This call returns the information of the online subscription. See section 2.2.4.52. The server MUST construct a response in either XML or JSON format based on the value of the Accept header (section 2.2.2.6), or in XML format if the Accept header is not present.
865.1.1.2 msolicense/set?localusername={localusername} This API sets the license to the online user, which is mapped to the local user. localusername: Local user name.
HTTP method Description
POST This API sets the license to the online user, which is mapped to the local user.
865.1.1.2.1 POST This API sets the license to the online user, which is mapped to the local user. This operation is transported by an HTTP POST. The operation can be invoked through the following URI:
866 https://
The request message for this operation contains the following HTTP headers. Request header Usage Value
Canary Optional The value returned in the logon Response Canary header. Client MUST either pass this header to the server or pass all of the following
106 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 Request header Usage Value
headers to the server. For more details, refer to section 2.2.2.5.
Authorization Optional The caller's credential is encoded text that is based on user name and password. For more details, refer to section 2.2.2.4.
AppName Optional Application name. For more details, refer to section 2.2.2.1.
AppVersion Optional Application version. For more details, refer to section 2.2.2.3.
AppPublisherName Optional Application publisher name. For more details, refer to section 2.2.2.2. The response message for this operation can result in the following status codes. Status code Description
200 Operation successfully completed.
400 Invalid parameter.
401 The user is not authorized for web access.
404 Cannot find the local user or online user.
500 Internal server error.
866.1.1.1.1.1Request Body The request body is encoded in XML format.
867
867.1.1.1.1.1Response Body None.
867.1.1.1.1.2Processing Details This API sets the license to the online user, which is mapped to the local user.
867.1.2 Timer Events None.
867.1.3 Other Local Events None.
867.2 IMailboxManagement Server Details
867.2.1 Abstract Data Model This section describes a conceptual service contract that an implementation maintains to participate in this protocol. The described operations of the service contract are provided to facilitate the explanation of how the protocol behaves. This document does not mandate that implementations adhere to this service contract as long as their external behavior is consistent with how it is described in this document.
107 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 867.2.1.1 Mailbox The data model uses full complex types defined in section 2.2.4.36.
867.2.1.2 ArrayOfMailbox The data model uses full complex types defined in section 2.2.4.10.
867.2.2 Timers None.
867.2.3 Initialization None.
867.2.4 Higher-Layer Triggered Events None.
867.2.5 Message Processing Events and Sequencing Rules
Resource Description mailbox?username={username} Retrieve the user's mailbox information. mailbox/create?username={username}&email={email} Create a mailbox for a user by using the default profile. mailbox/set?username={username}&email={email} Assign an existing mailbox to a user. mailbox/unset?username={username} Detach the mailbox from the user. mailbox/disable?username={username} Disable the mailbox. mailbox/delete?username={username} Delete the mailbox. mailbox/enable?username={username} Enable the mailbox. mailboxes Get all mailboxes. domains Get all accepted domains. mailbox/getemailaddresses?username={username} Get all email addresses. mailbox/setemailaddresses?username={username}&emails={emails} Set all email addresses. The responses to all the operations can result in the following status codes. Status code Reason phrase Description
200 OK The operation successfully completed.
400 Bad request Invalid parameter.
401 Unauthorized The user is not authorized for web access.
404 Not Found Cannot find the local user or online user.
500 Internal Server Error An internal server error occurred.
409 Conflict The operation failed because of the status conflict.
501 Not Implemented The operation is not supported.
403 Forbidden The operation is forbidden.
402 Payment Required No available licenses.
108 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 867.2.5.1 mailbox?username={username} Retrieves the mailbox assigned to the local user. username: Local user name.
HTTP method Description
GET Retrieves the mailbox assigned to the local user.
867.2.5.1.1 GET Retrieves the mailbox assigned to the local user. This operation is transported by an HTTP GET. The operation can be invoked through the following URI:
868 https://
The request message for this operation contains the following HTTP headers. Request header Usage Value
Canary Optional The user token. Client MUST either pass this header to the server or pass all of the following headers to the server. For more details, refer to section 2.2.2.5.
Authorization Optional The caller's credential is encoded text that is based on user name and password. For more details, refer to section 2.2.2.4.
AppName Optional The client application name. For more details, refer to section 2.2.2.1.
AppVersion Optional The client application version. For more details, refer to section 2.2.2.3.
AppPublisherName Optional The client application publisher name. For more details, refer to section 2.2.2.2. The response message for this operation can result in the following status codes. Status code Description
200 Operation successfully completed.
400 Invalid parameter.
401 The user is not authorized for web access.
404 Cannot find the local user or online user.
500 Internal server error.
868.1.1.1.1.1Request Body None.
868.1.1.1.1.2Response Body The response body is encoded in either XML or JSON format. The format is controlled by the Accept header defined in section 2.2.4.36.
869
869.1.1.1.1.1Processing Details This call returns the information of the mailbox. See section 2.2.4.36.
109 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 The server MUST construct a response in either XML or JSON format based on the value of the Accept header (section 2.2.2.6), or in XML format if the Accept header is not present.
869.1.1.2 mailbox/create?username={username}&email={email} Create a mailbox and assign to the local user. username: Local user name. email: Email address to create.
HTTP method Description
POST Create a mailbox and assign to the local user.
869.1.1.2.1 POST This operation is transported by an HTTP POST. The operation can be invoked through the following URI:
870 https://
The request message for this operation contains the following HTTP headers. Request header Usage Value
Canary Optional The user token. Client MUST either pass this header to the server or pass all of the following headers to the server. For more details, refer to section 2.2.2.5.
Authorization Optional The caller's credential is encoded text that is based on user name and password. For more details, refer to section 2.2.2.4.
AppName Optional The client application name. For more details, refer to section 2.2.2.1.
AppVersion Optional The client application version. For more details, refer to section 2.2.2.3.
AppPublisherName Optional The client application publisher name. For more details, refer to section 2.2.2.2. The response message for this operation can result in the following status codes. Status code Description
200 Operation successfully completed.
400 Invalid parameter.
401 The user is not authorized for web access.
404 Cannot find the local user or online user.
409 Operation failed because of the status conflict.
500 Internal server error.
870.1.1.1.1.1Request Body The request body is encoded in XML format or JSON format based on the value of the Accept header (section 2.2.2.6), or in XML format if the Accept header is not present.
110 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 870.1.1.1.1.2Response Body The response body is encoded in either XML or JSON format. The format is controlled by the Accept header defined in section 2.2.4.36.
870.1.1.1.1.3Processing Details This API creates a mailbox and assigns it to the local user.
870.1.1.2 mailbox/set?username={username}&email={email} Assign the mailbox to the local user. username: Local user name. email: Email address to assign to the local user.
HTTP method Description
POST Assign the mailbox to the local user.
870.1.1.2.1 POST This operation is transported by an HTTP POST. The operation can be invoked through the following URI:
871 https://
The request message for this operation contains the following HTTP headers. Request header Usage Value
Canary Optional The user token. Client MUST either pass this header to the server or pass all of the following headers to the server. For more details, refer to section 2.2.2.5.
Authorization Optional The caller's credential is encoded text that is based on user name and password. For more details, refer to section 2.2.2.4.
AppName Optional The client application name. For more details, refer to section 2.2.2.1.
AppVersion Optional The client application version. For more details, refer to section 2.2.2.3.
AppPublisherName Optional The client application publisher name. For more details, refer to section 2.2.2.2. The response message for this operation can result in the following status codes. Status code Description
200 Operation successfully completed.
400 Invalid parameter.
401 The user is not authorized for web access.
404 Cannot find the local user or online user.
409 Operation failed because of the status conflict.
500 Internal server error.
501 Operation is not supported.
871.1.1.1.1.1Request Body
111 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 None.
871.1.1.1.1.2Response Body None.
871.1.1.1.1.3Processing Details This API assigns the mailbox to the local user.
871.1.1.2 mailbox/unset?username={username} Detach the mailbox from the local user. username: Local user name.
HTTP method Description
POST Detach the mailbox from the local user.
871.1.1.2.1 POST This operation is transported by an HTTP POST. The operation can be invoked through the following URI:
872 https://
The request message for this operation contains the following HTTP headers. Request header Usage Value
Canary Optional The user token. Client MUST either pass this header to the server or pass all of the following headers to the server. For more details, refer to section 2.2.2.5.
Authorization Optional The caller's credential is encoded text that is based on user name and password. For more details, refer to section 2.2.2.4.
AppName Optional The client application name. For more details, refer to section 2.2.2.1.
AppVersion Optional The client application version. For more details, refer to section 2.2.2.3.
AppPublisherName Optional The client application publisher name. For more details, refer to section 2.2.2.2. The response message for this operation can result in the following status codes. Status code Description
200 Operation successfully completed.
400 Invalid parameter.
401 The user is not authorized for web access.
404 Cannot find the local user or online user.
409 Operation failed because of the status conflict.
500 Internal server error.
501 Operation is not supported.
872.1.1.1.1.1Request Body
112 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 None.
872.1.1.1.1.2Response Body None.
872.1.1.1.1.3Processing Details This API detaches the mailbox from the local user.
872.1.1.2 mailbox/disable?username={username} Disables the mailbox that is assigned to the local user. username: Local user name.
HTTP method Description
POST Disable the mailbox that is assigned to the local user.
872.1.1.2.1 POST This operation is transported by an HTTP POST. The operation can be invoked through the following URI:
873 https://
The request message for this operation contains the following HTTP headers. Request header Usage Value
Canary Optional The user token. Client MUST either pass this header to the server or pass all of the following headers to the server. For more details, refer to section 2.2.2.5.
Authorization Optional The caller's credential is encoded text that is based on user name and password. For more details, refer to section 2.2.2.4.
AppName Optional The client application name. For more details, refer to section 2.2.2.1.
AppVersion Optional The client application version. For more details, refer to section 2.2.2.3.
AppPublisherName Optional The client application publisher name. For more details, refer to section 2.2.2.2. The response message for this operation can result in the following status codes. Status code Description
200 Operation successfully completed.
400 Invalid parameter.
401 The user is not authorized for web access.
403 Operation is forbidden.
404 Cannot find the local user or online user.
500 Internal server error.
501 Operation is not supported.
873.1.1.1.1.1Request Body
113 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 None.
873.1.1.1.1.2Response Body None.
873.1.1.1.1.3Processing Details This API disables the mailbox that is assigned to the local user.
873.1.1.2 mailbox/delete?username={username} Delete the mailbox that is assigned to the local user. username: Local user name.
HTTP method Description
POST Delete the mailbox that is assigned to the local user.
873.1.1.2.1 POST This operation is transported by an HTTP POST. The operation can be invoked through the following URI:
874 https://
The request message for this operation contains the following HTTP headers. Request header Usage Value
Canary Optional The user token. Client MUST either pass this header to the server or pass all of the following headers to the server. For more details, refer to section 2.2.2.5.
Authorization Optional The caller's credential is encoded text that is based on user name and password. For more details, refer to section 2.2.2.4.
AppName Optional The client application name. For more details, refer to section 2.2.2.1.
AppVersion Optional The client application version. For more details, refer to section 2.2.2.3.
AppPublisherName Optional The client application publisher name. For more details, refer to section 2.2.2.2. The response message for this operation can result in the following status codes. Status code Description
200 Operation successfully completed.
400 Invalid parameter.
401 The user is not authorized for web access.
403 Operation is forbidden.
404 Cannot find the local user or online user.
500 Internal server error.
874.1.1.1.1.1Request Body The request body is encoded in XML format.
114 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 874.1.1.1.1.2Response Body None.
874.1.1.1.1.3Processing Details None.
874.1.1.2 mailbox/enable?username={username} Enable the mailbox that is assigned to the local user. username: Local user name.
HTTP method Description
POST Enable the mailbox that is assigned to the local user.
874.1.1.2.1 POST This operation is transported by an HTTP POST. The operation can be invoked through the following URI:
875 https://
The request message for this operation contains the following HTTP headers. Request header Usage Value
Canary Optional The user token. Client MUST either pass this header to the server or pass all of the following headers to the server. For more details, refer to section 2.2.2.5.
Authorization Optional The caller's credential is encoded text that is based on user name and password. For more details, refer to section 2.2.2.4.
AppName Optional The client application name. For more details, refer to section 2.2.2.1.
AppVersion Optional The client application version. For more details, refer to section 2.2.2.3.
AppPublisherName Optional The client application publisher name. For more details, refer to section 2.2.2.2. The response message for this operation can result in the following status codes. Status code Description
200 Operation successfully completed.
400 Invalid parameter.
401 The user is not authorized for web access.
404 Cannot find the local user or online user.
500 Internal server error.
501 Operation is not supported.
875.1.1.1.1.1Request Body None.
875.1.1.1.1.2Response Body
115 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 None.
875.1.1.1.1.3Processing Details This API enables the mailbox that is assigned to the local user.
875.1.1.2 mailboxes Retrieve all the mailboxes. HTTP method Description
GET Retrieve all the mailboxes
875.1.1.2.1 GET This operation is transported by an HTTP GET. The operation can be invoked through the following URI:
876 https://
The request message for this operation contains the following HTTP headers. Request header Usage Value
Canary Optional The user token. Client MUST either pass this header to the server or pass all of the following headers to the server. For more details, refer to section 2.2.2.5.
Authorization Optional The caller's credential is encoded text that is based on user name and password. For more details, refer to section 2.2.2.4.
AppName Optional The client application name. For more details, refer to section 2.2.2.1.
AppVersion Optional The client application version. For more details, refer to section 2.2.2.3.
AppPublisherName Optional The client application publisher name. For more details, refer to section 2.2.2.2. The response message for this operation can result in the following status codes. Status code Description
200 Operation successfully completed.
400 Invalid parameter.
401 The user is not authorized for web access.
500 Internal server error.
876.1.1.1.1.1Request Body None.
876.1.1.1.1.2Response Body The response body is encoded in either XML or JSON format. The format is controlled by the Accept header defined in section 2.2.4.10.
877
877.1.1.1.1.1Processing Details This call returns the information of all the mailboxes. See section 2.2.4.10.
116 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 The server MUST construct a response in either XML or JSON format based on the value of the Accept header (section 2.2.2.6), or in XML format if the Accept header is not present.
877.1.1.2 domains Retrieve all the accepted domains. HTTP method Description
GET Retrieve all the accepted domains.
877.1.1.2.1 GET This operation is transported by an HTTP GET. The operation can be invoked through the following URI:
878 https://
The request message for this operation contains the following HTTP headers. Request header Usage Value
Canary Optional The user token. Client MUST either pass this header to the server or pass all of the following headers to the server. For more details, refer to section 2.2.2.5.
Authorization Optional The caller's credential is encoded text that is based on user name and password. For more details, refer to section 2.2.2.4.
AppName Optional The client application name. For more details, refer to section 2.2.2.1.
AppVersion Optional The client application version. For more details, refer to section 2.2.2.3.
AppPublisherName Optional The client application publisher name. For more details, refer to section 2.2.2.2. The response message for this operation can result in the following status codes. Status code Description
200 Operation successfully completed.
400 Invalid parameter.
401 The user is not authorized for web access.
500 Internal server error.
878.1.1.1.1.1Request Body None.
878.1.1.1.1.2Response Body The response body is encoded in either XML or JSON format. The format is controlled by the Accept header defined in section 2.2.4.21.
879
879.1.1.1.1.1Processing Details This call returns the information of the SharePoint site. See section 2.2.4.21.
117 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 The server MUST construct a response in either XML or JSON format based on the value of the Accept header (section 2.2.2.6), or in XML format if the Accept header is not present.
879.1.1.2 mailbox/getemailaddresses?username={username} Retrieve all the email addresses that are assigned to the user. username:
HTTP method Description
GET Retrieve all the email addresses that are assigned to the user.
879.1.1.2.1 GET This operation is transported by an HTTP GET. The operation can be invoked through the following URI:
880 https://
The request message for this operation contains the following HTTP headers. Request header Usage Value
Canary Optional The user token. Client MUST either pass this header to the server or pass all of the following headers to the server. For more details, refer to section 2.2.2.5.
Authorization Optional The caller's credential is encoded text that is based on user name and password. For more details, refer to section 2.2.2.4.
AppName Optional The client application name. For more details, refer to section 2.2.2.1.
AppVersion Optional The client application version. For more details, refer to section 2.2.2.3.
AppPublisherName Optional The client application publisher name. For more details, refer to section 2.2.2.2. The response message for this operation can result in the following status codes. Status code Description
200 Operation successfully completed.
400 Invalid parameter.
401 The user is not authorized for web access.
404 Cannot find the local user or online user.
500 Internal server error.
501 Operation is not supported.
880.1.1.1.1.1Request Body None.
880.1.1.1.1.2Response Body The response body is encoded in either XML or JSON format. The format is controlled by the Accept header defined in section 2.2.4.21.
118 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 880.1.1.1.1.3Processing Details This call returns the information of the email addresses. See section 2.2.4.21. The server MUST construct a response in either XML or JSON format based on the value of the Accept header (section 2.2.2.6), or in XML format if the Accept header is not present.
880.1.1.2 mailbox/setemailaddresses?username={username}&emails={emails} Set the email addresses for the user. username: Local user name. emails: Email addresses.
HTTP method Description
POST Set the email addresses for the user.
880.1.1.2.1 POST This operation is transported by an HTTP POST. The operation can be invoked through the following URI:
881 https://
The request message for this operation contains the following HTTP headers. Request header Usage Value
Canary Optional The user token. Client MUST either pass this header to the server or pass all of the following headers to the server. For more details, refer to section 2.2.2.5.
Authorization Optional The caller's credential is encoded text that is based on user name and password. For more details, refer to section 2.2.2.4.
AppName Optional The client application name. For more details, refer to section 2.2.2.1.
AppVersion Optional The client application version. For more details, refer to section 2.2.2.3.
AppPublisherName Optional The client application publisher name. For more details, refer to section 2.2.2.2. The response message for this operation can result in the following status codes. Status code Description
200 Operation successfully completed.
400 Invalid parameter.
401 The user is not authorized for web access.
402 No available licenses.
404 Cannot find the local user or online user.
500 Internal server error.
501 Operation is not supported.
881.1.1.1.1.1Request Body None.
119 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 881.1.1.1.1.2Response Body None.
881.1.1.1.1.3Processing Details This API sets the email addresses for the user.
881.1.2 Timer Events None.
881.1.3 Other Local Events None.
881.2 IAlertManagement Server Details
881.2.1 Abstract Data Model This section describes a conceptual service contract that an implementation maintains to participate in this protocol. The described operations of the service contract are provided to facilitate the explanation of how the protocol behaves. This document does not mandate that implementations adhere to this service contract as long as their external behavior is consistent with how it is described in this document.
881.2.1.1 AlertInfo The AlertInfo data model has a full complex type defined in section 2.2.4.1. Severity: The health status:
OK: There is no existing alert.
Information: Informational alert.
Warning: Warning alert.
Critical: Critical alert.
Report: An alert that collects information from the client.
881.2.2 Timers None.
881.2.3 Initialization None.
881.2.4 Higher-Layer Triggered Events None.
120 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 881.2.5 Message Processing Events and Sequencing Rules
Resource Description alerts/index/{startingindex}/count/{amount} Retrieves all health alerts in the network. alert/enable?alertkey={alertkey} Enables an ignored alert. alert/disable?alertkey={alertkey} Disables an alert. alert/clear?alertkey={alertkey} Clears an alert. alert/repair?alertkey={alertkey} Attempts to repair an alert. The responses to all the operations can result in the following status codes. Status code Reason phrase Description
200 OK Operation successfully completed.
400 Bad Request One or more parameters are not valid.
401 Unauthorized Access to the requested resource is denied.
404 Not Found The specific resource does not exist.
881.2.5.1 alerts/index/{startingindex}/count/{amount} Retrieves all health alerts in the network. startingindex: The numerical position of the first item to be retrieved. See section 2.2.3.45. amount: The number of items to be retrieved. See section 2.2.3.2.
HTTP method Description
GET Retrieves all health alerts in the network.
881.2.5.1.1 GET Retrieves all health alerts in the network. This operation is transported by an HTTP GET. The operation can be invoked through the following URI:
882 alerts/index/{startingindex}/count/{amount}
The request message for this operation contains the following HTTP headers. Request header Usage Value
Canary Optional The user token. Client MUST either pass this header to the server or pass all of the following headers to the server. For more details, refer to section 2.2.2.5.
Authorization Optional The caller's credential is encoded text that is based on user name and password. For more details, refer to section 2.2.2.4.
AppName Optional The client application name. For more details, refer to section 2.2.2.1.
AppVersion Optional The client application version. For more details, refer to section 2.2.2.3.
AppPublisherName Optional The client application publisher name. For more details, refer to section 2.2.2.2. The response message for this operation can result in the following status codes. Status code Description
200 Operation successfully completed.
121 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 Status code Description
400 One or more parameters are not valid.
401 Access to the requested resource is denied.
882.1.1.1.1.1Request Body None.
882.1.1.1.1.2Response Body The response body is encoded in either XML or JSON format. The format is controlled by the Accept header defined in section 2.2.2.6.
883
883.1.1.1.1.1Processing Details This call returns the PartialCollection, which contains the instances of AlertInfo specified by startingIndex and amount. The server MUST construct a response in either XML or JSON format based on the value of the Accept header (section 2.2.2.6), or in XML format if the Accept header is not present.
883.1.1.2 alert/enable?alertkey={alertkey} This API enables an ignored alert that is identified by the alert key. alertkey: The key of the alert. See section 2.2.3.1.
HTTP method Description
POST Enables an ignored alert.
883.1.1.2.1 POST This API enables an ignored alert. The alert is identified by the alert key. This operation is transported by an HTTP POST. The operation can be invoked through the following URI:
884 https://
The request message for this operation contains the following HTTP headers. Request header Usage Value
Canary Optional The user token. Client MUST either pass this header to the server or pass all of the following headers to the server. For more details, refer to section 2.2.2.5.
Authorization Optional The caller's credential is encoded text that is based on user name and password. For more details, refer to section 2.2.2.4.
AppName Optional The client application name. For more details, refer to section 2.2.2.1.
AppVersion Optional The client application version. For more details, refer to section 2.2.2.3.
122 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 Request header Usage Value
AppPublisherName Optional The client application publisher name. For more details, refer to section 2.2.2.2. The response message for this operation can result in the following status codes. Status code Description
200 The operation successfully completed.
400 One or more parameters are not valid.
401 Access to the requested resource is denied.
404 The alert specified by the alert key does not exist.
884.1.1.1.1.1Request Body None.
884.1.1.1.1.2Response Body None.
884.1.1.1.1.3Processing Details This call enables a network health alert.
884.1.1.2 alert/disable?alertkey={alertkey} This API is for disabling an alert. alertkey: The key of the alert. See section 2.2.3.1.
HTTP method Description
POST Disables an alert.
884.1.1.2.1 POST This operation disables an alert and is transported by an HTTP POST. The operation can be invoked through the following URI:
885 https://
The request message for this operation contains the following HTTP headers. Request header Usage Value
Canary Optional The user token. Client MUST either pass this header to the server or pass all of the following headers to the server. For more details, see section 2.2.2.5.
Authorization Optional The caller's credential is encoded text that is based on user name and password. For more details, see section 2.2.2.4.
AppName Optional The client application name. For more details, see section 2.2.2.1.
AppVersion Optional The client application version. For more details, see section 2.2.2.3.
AppPublisherName Optional The client application publisher name. For more details, see section 2.2.2.2.
123 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 The response message for this operation can result in the following status codes. Status code Description
200 Operation successfully completed.
400 One or more parameters are not valid.
401 Access to the requested resource is denied.
404 The alert specified by the alert key does not exist.
885.1.1.1.1.1Request Body None.
885.1.1.1.1.2Response Body None.
885.1.1.1.1.3Processing Details This call disables a network health alert.
885.1.1.2 alert/clear?alertkey={alertkey} This API clears an alert given the key of the alert. alertkey: The key of the alert. See section 2.2.3.1.
HTTP method Description
POST Clears an alert.
885.1.1.2.1 POST This operation clears an alert and is transported by an HTTP POST. The operation can be invoked through the following URI:
886 https://
The request message for this operation contains the following HTTP headers. Request header Usage Value
Canary Optional The user token. Client MUST either pass this header to the server or pass all of the following headers to the server. For more details, refer to section 2.2.2.5.
Authorization Optional The caller's credential is encoded text that is based on user name and password. For more details, refer to section 2.2.2.4.
AppName Optional The client application name. For more details, refer to section 2.2.2.1.
AppVersion Optional The client application version. For more details, refer to section 2.2.2.3.
AppPublisherName Optional The client application publisher name. For more details, refer to section 2.2.2.2. The response message for this operation can result in the following status codes. Status code Description
200 Operation successfully completed.
124 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 Status code Description
400 One or more parameters are not valid.
401 Access to the requested resource is denied.
404 The alert specified by the alert key does not exist.
886.1.1.1.1.1Request Body None.
886.1.1.1.1.2Response Body None.
886.1.1.1.1.3Processing Details This call clears a network health alert.
886.1.1.2 alert/repair?alertkey={alertkey} This API attempts to repair an alert if the alert is reparable. alertkey: The key of the alert. See section 2.2.3.1.
HTTP method Description
POST Attempts to repair an alert.
886.1.1.2.1 POST This operation attempts to repair an alert. It is transported by an HTTP POST. The operation can be invoked through the following URI:
887 https://
The request message for this operation contains the following HTTP headers. Request header Usage Value
Canary Optional The user token. Client MUST either pass this header to the server or pass all of the following headers to the server. For more details, refer to section 2.2.2.5.
Authorization Optional The caller's credential is encoded text that is based on user name and password. For more details, refer to section 2.2.2.4.
AppName Optional The client application name. For more details, refer to section 2.2.2.1.
AppVersion Optional The client application version. For more details, refer to section 2.2.2.3.
AppPublisherName Optional The client application publisher name. For more details, refer to section 2.2.2.2. The response message for this operation can result in the following status codes. Status code Description
200 Operation successfully completed.
400 One or more parameters are not valid.
125 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 Status code Description
401 Access to the requested resource is denied.
404 The alert specified by the alert key does not exist.
887.1.1.1.1.1Request Body None.
887.1.1.1.1.2Response Body None.
887.1.1.1.1.3Processing Details This call attempts to repair a network health alert.
887.1.2 Timer Events None.
887.1.3 Other Local Events None.
887.2 IDeviceManagement Server Details
887.2.1 Abstract Data Model This section describes a conceptual service contract that an implementation maintains to participate in this protocol. The described operations of the service contract are provided to facilitate the explanation of how the protocol behaves. This document does not mandate that implementations adhere to this service contract as long as their external behavior is consistent with how it is described in this document.
887.2.1.1 DeviceInfo The DeviceInfo data model has a full complex type defined in section 2.2.4.28.
887.2.2 Timers None.
887.2.3 Initialization None.
887.2.4 Higher-Layer Triggered Events None.
126 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 887.2.5 Message Processing Events and Sequencing Rules
Resource Description devices/index/{startingindex}/count/{amount} Retrieves a list of devices that are managed by the server. device/{deviceid}/startbackup Starts to back up a device that is managed by the server. device/{deviceid}/stopbackup Stops the backup of a device that is managed by the server. The responses to all the operations can result in the following status codes. Status code Reason phrase Description
200 OK The operation successfully completed.
400 Bad Request One or more parameters are not valid.
401 Unauthorized Access to the requested resource is denied.
404 Not Found Resource not found.
403 Forbidden The operation is forbidden.
887.2.5.1 devices/index/{startingindex}/count/{amount} Retrieves a list of devices that are managed by the server. startingindex: The numerical position of the first item to be retrieved. It SHOULD be a string that can be converted to a positive integer. See section 2.2.3.45. amount: The number of items to be retrieved. It SHOULD be a string that can be converted to a positive integer. See section 2.2.3.2.
HTTP method Description
GET Retrieves a list of devices that are managed by the server, or the devices that the current standard user has remote access permission to.
887.2.5.1.1 GET Retrieves a list of devices that are managed by the server.<11> This operation is transported by an HTTP GET. The operation can be invoked through the following URI:
888 https://
The request message for this operation contains the following HTTP headers. Request header Usage Value
Canary Optional The user token. Client MUST either pass this header to the server or pass all of the following headers to the server. For more details, refer to section 2.2.2.5.
Authorization Optional The caller's credential is encoded text that is based on user name and password. For more details, refer to section 2.2.2.4.
AppName Optional The client application name. For more details, refer to section 2.2.2.1.
AppVersion Optional The client application version. For more details, refer to section 2.2.2.3.
AppPublisherName Optional The client application publisher name. For more details, refer to section 2.2.2.2.
127 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 The response message for this operation can result in the following status codes. Status code Description
200 Operation successfully completed.
400 One or more parameters are not valid.
401 Access to the requested resource is denied.
404 The requested resource does not exist.
888.1.1.1.1.1Request Body None.
888.1.1.1.1.2Response Body The response body is encoded in either XML or JSON format. The format is controlled by the Accept header defined in section 2.2.2.6.
889
889.1.1.1.1.1Processing Details This call returns the PartialCollection, which contains the instances of DeviceInfo specified by startingIndex and amount. The server MUST construct a response in either XML or JSON format based on the value of the Accept header (section 2.2.2.6), or in XML format if the Accept header is not present.
889.1.1.2 device/{deviceid}/startbackup Starts to back up a device that is managed by the server. deviceid: The ID of the device; see section 2.2.3.8.
HTTP method Description
POST Starts to back up a device that is managed by the server.
889.1.1.2.1 POST Starts to back up a device that is managed by the server. This operation is transported by an HTTP POST. The operation can be invoked through the following URI:
890 https://
The request message for this operation contains the following HTTP headers. Request header Usage Value
Canary Optional The user token. Client MUST either pass this header to the server or pass all of the following headers to the server. For more details, refer to section 2.2.2.5.
Authorization Optional The caller's credential is encoded text that is based on user name and password.
128 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 Request header Usage Value
For more details, refer to section 2.2.2.4.
AppName Optional The client application name. For more details, refer to section 2.2.2.1.
AppVersion Optional The client application version. For more details, refer to section 2.2.2.3.
AppPublisherName Optional The client application publisher name. For more details, refer to section 2.2.2.2. The response message for this operation can result in the following status codes. Status code Description
200 Operation successfully completed.
400 One or more parameters are not valid.
401 Access to the requested resource is denied. This API only supports Administrator calls.
403 Another backup is already in progress.
404 The device specified by DeviceId does not exist.
890.1.1.1.1.1Request Body None.
890.1.1.1.1.2Response Body None.
890.1.1.1.1.3Processing Details The server MUST enable the backup feature to support backup. This call starts to backup the specific device.
890.1.1.2 device/{deviceid}/stopbackup Stops the backup of a device that is managed by the server. deviceid: The ID of the device; see section 2.2.3.8.
HTTP method Description
POST Stops the backup of a device that is managed by the server.
890.1.1.2.1 POST Stops the backup of a device that is managed by the server. This operation is transported by an HTTP POST. The operation can be invoked through the following URI:
891 Https://
The request message for this operation contains the following HTTP headers. Request header Usage Value
Canary Optional The user token. Client MUST either pass this header to the server or pass all of the following headers to the server. For more details, refer to section 2.2.2.5.
129 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 Request header Usage Value
Authorization Optional The caller's credential is encoded text that is based on user name and password. For more details, refer to section 2.2.2.4.
AppName Optional The client application name. For more details, refer to section 2.2.2.1.
AppVersion Optional The client application version. For more details, refer to section 2.2.2.3.
AppPublisherName Optional The client application publisher name. For more details, refer to section 2.2.2.2. The response message for this operation can result in the following status codes. Status code Description
200 Operation successfully completed.
400 One or more parameters are not valid.
401 Access to the requested resource is denied. This API only supports Administrator calls.
403 The backup has already been stopped.
404 The device specified by DeviceId does not exist.
891.1.1.1.1.1Request Body None.
891.1.1.1.1.2Response Body None.
891.1.1.1.1.3Processing Details Server MUST enable the backup feature to support backup. This call stops the processing backup for the specific device.
891.1.2 Timer Events None.
891.1.3 Other Local Events None.
891.2 IServiceManagement Server Details
891.2.1 Abstract Data Model This section describes a conceptual service contract that an implementation maintains to participate in this protocol. The described operations of the service contract are provided to facilitate the explanation of how the protocol behaves. This document does not mandate that implementations adhere to this service contract as long as their external behavior is consistent with how it is described in this document.
130 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 891.2.1.1 WebApiProvider The WebApiProvider data model has a full complex type defined in section 2.2.4.72.
891.2.2 Timers None.
891.2.3 Initialization None.
891.2.4 Higher-Layer Triggered Events None.
891.2.5 Message Processing Events and Sequencing Rules
Resource Description permittedbuiltinservices Retrieves the other services that the current logged-in user has access to. The responses to all the operations can result in the following status codes. Status code Reason phrase Description
200 OK The operation successfully completed.
401 Unauthorized Access to the requested resource is denied.
891.2.5.1 permittedbuiltinservices
HTTP method Description
GET Retrieves the other services that the current logged-in user has access to.
891.2.5.1.1 GET Retrieves the other services that the current logged-in user has access to. This operation is transported by an HTTP GET. The operation can be invoked through the following URI:
892 https://
The request message for this operation contains the following HTTP headers. Request header Usage Value
Canary Optional The user token. Client MUST either pass this header to the server or pass all of the following headers to the server. For more details, refer to section 2.2.2.5.
Authorization Optional The caller's credential is encoded text that is based on user name and password. For more details, refer to section 2.2.2.4.
AppName Optional The client application name. For more details, refer to section 2.2.2.1.
AppVersion Optional The client application version. For more details, refer to section 2.2.2.3.
AppPublisherName Optional The client application publisher name. For more details, refer to section 2.2.2.2.
131 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 The response message for this operation can result in the following status codes. Status code Description
200 Operation successfully completed.
401 Access to the requested resource is denied.
892.1.1.1.1.1Request Body None.
892.1.1.1.1.2Response Body The response body is encoded in either XML or JSON format. The format is controlled by the Accept header defined in section 2.2.2.6.
893
893.1.1.1.1.1Processing Details This call returns a list of other WebApi provider services that the current logged-in user has permission to access. The server MUST construct a response in either XML or JSON format based on the value of the Accept header (section 2.2.2.6), or in XML format if the Accept header is not present.
893.1.2 Timer Events None.
893.1.3 Other Local Events None.
893.2 IServerManagement Server Details
893.2.1 Abstract Data Model This section describes a conceptual service contract that an implementation maintains to participate in this protocol. The described operations of the service contract are provided to facilitate the explanation of how the protocol behaves. This document does not mandate that implementations adhere to this service contract as long as their external behavior is consistent with how it is described in this document.
893.2.1.1 WebApiProvider The WebApiProvider data model has a full complex type defined in section 2.2.4.67.
132 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 893.2.2 Timers None.
893.2.3 Initialization None.
893.2.4 Higher-Layer Triggered Events None.
893.2.5 Message Processing Events and Sequencing Rules
Resource Description serverinformation Retrieves the basic server information to the client, such as the server name and the server SKU. The responses to all the operations can result in the following status codes. Status code Reason phrase Description
200 OK The operation successfully completed.
401 Unauthorized Access to the requested resource is denied. The request MUST contain the authentication information.
893.2.5.1 serverinformation
HTTP method Description
GET Retrieves the basic server information to the client, such as the server name and the server SKU.
893.2.5.1.1 GET Retrieves the basic server information to the client, such as the server name and the server SKU. This operation is transported by an HTTP GET. The operation can be invoked through the following URI:
894 https://
The request message for this operation contains the following HTTP headers. Request header Usage Value
Canary Optional The user token. Client MUST either pass this header to the server or pass all of the following headers to the server. For more details, refer to section 2.2.2.5.
Authorization Optional The caller's credential is encoded text that is based on user name and password. For more details, refer to section 2.2.2.4.
AppName Optional The client application name. For more details, refer to section 2.2.2.1.
AppVersion Optional The client application version. For more details, refer to section 2.2.2.3.
AppPublisherName Optional The client application publisher name. For more details, refer to section 2.2.2.2. The response message for this operation can result in the following status codes.
133 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 Status code Description
200 Operation successfully completed.
401 Access to the requested resource is denied.
894.1.1.1.1.1Request Body None.
894.1.1.1.1.2Response Body The response body is encoded in either XML or JSON format. The format is controlled by the Accept header defined in section 2.2.2.6.
895
895.1.1.1.1.1Processing Details This call returns an instance of complex type of ServerInfo; see section 2.2.4.67. The server MUST construct a response in either XML or JSON format based on the value of the Accept header (section 2.2.2.6), or in XML format if the Accept header is not present.
895.1.2 Timer Events None.
895.1.3 Other Local Events None.
895.2 ICustomizationManagement Server Details
895.2.1 Abstract Data Model This section describes a conceptual service contract that an implementation maintains to participate in this protocol. The described operations of the service contract are provided to facilitate the explanation of how the protocol behaves. This document does not mandate that implementations adhere to this service contract as long as their external behavior is consistent with how it is described in this document.
895.2.1.1 CustomizationInfo The data model uses full complex types defined in section 2.2.4.27, section 2.2.4.9, and section 2.2.4.35.
895.2.2 Timers None.
134 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 895.2.3 Initialization None.
895.2.4 Higher-Layer Triggered Events None.
895.2.5 Message Processing Events and Sequencing Rules Retrieves the customization information. Resource Description customizationinformation Retrieves the customization information. The responses to all the operations can result in the following status codes. Status code Reason phrase Description
200 OK Operation successfully completed.
404 Not Found Cannot find the customization information from the server.
895.2.5.1 customizationinformation Retrieves the customization information. HTTP method Description
GET Retrieves the customization information.
895.2.5.1.1 GET Retrieves the customization information. This operation is transported by an HTTP GET. The operation can be invoked through the following URI:
896 https://
The response message for this operation can result in the following status codes. Status code Description
200 Operation successfully completed.
404 Cannot found the customization information from server.
896.1.1.1.1.1Request Body None.
896.1.1.1.1.2Response Body The response body is encoded in either XML or JSON format. The format is controlled by the Accept header defined in section 2.2.2.6.
135 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 897
897.1.1.1.1.1Processing Details 1. This call returns an instance of the complex type CustomizationInfo; see section 2.2.4.27. 2. The server MUST construct a response in either XML or JSON format based on the value of the Accept header (section 2.2.2.6), or in XML format if the Accept header is not present. 3. The server initializes the customization information.
897.1.2 Timer Events None.
897.1.3 Other Local Events None.
897.2 IMediaManagement Server Details
897.2.1 Abstract Data Model None.
897.2.2 Timers None.
897.2.3 Initialization At initialization time, the protocol server MUST begin listening for requests at the respective URL addresses given in the message transport, as specified in section 2.1. Media feature MUST be initialized on the server.<12>
897.2.4 Higher-Layer Triggered Events None.
897.2.5 Message Processing Events and Sequencing Rules
Desc ripti Resource on metadata/item/mediatype/{mediatypedata}/groupingmethod/{groupingmethoddata}/sortproperty/ The {sortpropertydata}/sortorder/{sortorderdata}/index/{startingindexdata}/count/{requestedcountdata}? meta grouping={groupingdata} data of medi a items of a certai
136 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 Desc ripti Resource on
n medi a type with the specif ied sortin g and group ing optio ns. metadata/container/mediatype/{mediatypedata}/groupingmethod/{groupingmethoddata}? Detail path={containerpath} ed infor matio n about a meta data conta iner. search/mediatype/{mediatypedata}/groupingmethod/{groupingmethoddata}/index/ Searc {startingindexdata}/count/{requestedcountdata}? h keywords={keywords}&grouping={groupingdata}&titleonly={titleonlydata}&shallow={shallowdata} result for medi a items that conta in certai n keyw ords. photo/{id}/isoriginal/{isoriginaldata}/width/{widthdata}/height/{heightdata} A photo with a certai n size. thumbnail/mediatype/{mediatypedata}/id/{id}/width/{widthdata}/height/{heightdata} The thum bnail of pictur e, video , and albu m art of the music with a certai
137 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 Desc ripti Resource on
n size. testdata?sizedata={sizedata} Data of a certai n size to be sent to the client to help calcul ate the availa ble band width . metadata/streams/mediatype/{mediatypedata}/id/{id}/index/{startingindexdata}/count/ Infor {requestedcountdata} matio n about the availa ble strea ms for an audio or video item. The responses to all the operations can result in the following status codes. Status code Reason phrase Description
200 OK The operation successfully completed.
400 Bad Request One or more parameters are not valid.
401 Unauthorized Access to the requested resource is denied.
404 Not Found The path does not exist.
897.2.5.1 metadata/item/mediatype/{mediatypedata}/groupingmethod/ {groupingmethoddata}/sortproperty/{sortpropertydata}/sortorder/ {sortorderdata}/index/{startingindexdata}/count/{requestedcountdata}? grouping={groupingdata} This method retrieves the metadata of media items of a certain media type with the specified sorting and grouping options. mediatypedata: The media type. See section 2.2.3.24. groupingmethoddata: The grouping method. See section 2.2.3.15.
138 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 groupingdata: The container path. See section 2.2.3.14. startingindexdata: The numerical position of the first media item to be retrieved. See section 2.2.3.46. requestedcountdata: The requested number of media items to be retrieved. See section 2.2.3.36. sortpropertydata: The metadata property on which to sort the media items. See section 2.2.3.44. sortorderdata: The sort order. See section 2.2.3.43.
HTTP method Description
GET Retrieves the metadata of media items of a certain media type with the specified sorting and grouping options.
897.2.5.1.1 GET This operation is transported by an HTTP GET. The operation can be invoked through the following URI:
898 metadata/item/mediatype/{mediatypedata}/groupingmethod/ {groupingmethoddata}/sortproperty/{sortpropertydata}/sortorder/{sortorderdata}/index/ {startingindexdata}/count/{requestedcountdata}?grouping={groupingdata}
The request message for this operation contains the following HTTP headers. Request header Usage Value
Canary Optional The value returned in the logon Response Canary header. Client MUST either pass this header to the server or pass all of the following headers to the server. For more details, see section 2.2.2.5.
Authorization Optional The caller's credential is encoded text that is based on user name and password. For more details, see section 2.2.2.4.
AppName Optional Application name. For more details, see section 2.2.2.1.
AppVersion Optional Application version. For more details, see section 2.2.2.3.
AppPublisherName Optional Application publisher name. For more details, see section 2.2.2.2. The response message for this operation can result in the following status codes. Status code Description
200 Operation successfully completed.
400 One or more parameters are not valid.
401 Access to the requested resource is denied.
404 The path does not exist.
898.1.1.1.1.1Request Body None.
898.1.1.1.1.2Response Body The response body is encoded in either XML or JSON format. The format is controlled by the Accept header.
139 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 899
899.1.1.1.1.1Processing Details 1. The server MUST only respond to requests that have established TLS 1.1 server authentication [RFC4346]. 2. The server MUST construct a response in either XML or JSON format based on the value of the Accept header or XML if the Accept header was not present. 3. The server MUST retrieve the metadata of media items of a certain media type with the specified sorting and grouping options, and fill the response body with type MetadataResult defined in section 2.2.4.45.
899.1.1.2 metadata/container/mediatype/{mediatypedata}/groupingmethod/ {groupingmethoddata}?path={containerpath} Retrieves detailed information about a metadata container. mediatypedata: The media type. See section 2.2.3.24. groupingmethoddata: The grouping method. See section 2.2.3.15. containerpath: The path to the container. See section 2.2.3.4.
HTTP method Description
GET Retrieves detailed information about a metadata container.
899.1.1.2.1 GET Retrieves detailed information about a metadata container. This operation is transported by an HTTP GET. The operation can be invoked through the following URI:
900 metadata/container/mediatype/{mediatypedata}/groupingmethod/{groupingmethoddata}? path={containerpath}
The request message for this operation contains the following HTTP headers. Request header Usage Value
Canary Optional The value returned in the logon Response Canary header. Client MUST either pass this header to the server or pass all of the following headers to the server. For more details, see section 2.2.2.5.
Authorization Optional The caller's credential is encoded text that is based on user name and password. For more details, see section 2.2.2.4.
AppName Optional Application name. For more details, see section 2.2.2.1.
AppVersion Optional Application version. For more details, see section 2.2.2.3.
AppPublisherName Optional Application publisher name. For more details, see section 2.2.2.2. The response message for this operation can result in the following status codes.
140 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 Status code Description
200 Operation successfully completed.
400 One or more parameters are not valid.
401 Access to the requested resource is denied.
404 The path does not exist.
900.1.1.1.1.1Request Body None.
900.1.1.1.1.2Response Body The response body is encoded in either Xml or JSON format. The format is controlled by the Accept header.
901
901.1.1.1.1.1Processing Details 1. The server MUST only respond to requests that have established TLS 1.1 server authentication [RFC4346]. 2. The server MUST construct a response in either XML or JSON format based on the value of the Accept header or XML if the Accept header was not present. 3. The server MUST retrieve the metadata of media items of a certain media type with the specified sorting and grouping options, and fill the response body with type MetadataDetailResult defined in section 2.2.4.42.
901.1.1.2 search/mediatype/{mediatypedata}/groupingmethod/ {groupingmethoddata}/index/{startingindexdata}/count/ {requestedcountdata}? keywords={keywords}&grouping={groupingdata}&titleonly={titleonlydata}&s hallow={shallowdata} Get the sub-item count for certain container. This API is deprecated. mediatypedata: The media type. See section 2.2.3.24. groupingmethoddata: The grouping method. See section 2.2.3.15. groupingdata: The path to the container. See section 2.2.3.14. keywords: A space-separated list of keywords to search for. See section 2.2.3.20. startingindexdata: The numerical position of the first media item to be retrieved. See section 2.2.3.46. requestedcountdata: The requested number of media items to be retrieved. See section 2.2.3.36. titleonlydata: Whether the search is performed on title only. See section 2.2.3.48. shallowdata: Whether the search is shallow or deep. See section 2.2.3.39.
HTTP method Description
GET Searches for media items that contain certain keywords.
141 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 HTTP method Description
901.1.1.2.1 GET Searches for media items that contain certain keywords. This operation is transported by an HTTP GET. The operation can be invoked through the following URI:
902 search/mediatype/{mediatypedata}/groupingmethod/{groupingmethoddata}/index/ {startingindexdata}/count/{requestedcountdata}? keywords={keywords}&grouping={groupingdata}&titleonly={titleonlydata}&shallow={shallowdata}
The request message for this operation contains the following HTTP headers. Request header Usage Value
Canary Optional The value returned in the logon Response Canary header. Client MUST either pass this header to the server or pass all of the following headers to the server. For more details, see section 2.2.2.5.
Authorization Optional The caller's credential is encoded text that is based on user name and password. For more details, see section 2.2.2.4.
AppName Optional Application name. For more details, see section 2.2.2.1.
AppVersion Optional Application version. For more details, see section 2.2.2.3.
AppPublisherName Optional Application publisher name. For more details, see section 2.2.2.2. The response message for this operation can result in the following status codes. Status code Description
200 Operation successfully completed.
400 One or more parameters are not valid.
401 Access to the requested resource is denied.
404 The path does not exist.
902.1.1.1.1.1Request Body None.
902.1.1.1.1.2Response Body The response body is encoded in Xml format.
902.1.1.1.1.3Processing Details The server MUST only respond to requests that have established TLS 1.1 server authentication as specified in [RFC4346]. The server MUST construct a response in either XML or JSON format based on the value of the Accept header or Xml if the Accept header was not present. The server MUST searches for media items that contain certain keywords, and fill the response body with type MetadataResult defined in section 2.2.4.45.
142 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 902.1.1.2 photo/{id}/isoriginal/{isoriginaldata}/width/{widthdata}/height/ {heightdata} This method retrieves a photo of a certain size. id: The photo identifier. See section 2.2.3.17. isoriginaldata: Specify whether to return the original data. If yes, widthdata and heightdata will not take effect, but they’re still required in the request. See section 2.2.3.19. widthdata: The width of an image. This value is required, but it is ignored if isoriginaldata is TRUE. See section 2.2.3.54. heightdata: The width of the photo. This value is required, but it is ignored if isoriginaldata is TRUE. See section 2.2.3.16.
HTTP method Description
GET Retrieve a photo of a certain size.
902.1.1.2.1 GET This operation is transported by an HTTP GET. The operation can be invoked through the following URI:
903 photo/{id}/isoriginal/{isoriginaldata}/width/{widthdata}/height/{heightdata}
The request message for this operation contains the following HTTP headers. Request header Usage Value
Canary Optional The value returned in the logon Response Canary header. Client MUST either pass this header to the server or pass all of the following headers to the server. For more details, see section 2.2.2.5.
Authorization Optional The caller's credential is encoded text that is based on user name and password. For more details, see section 2.2.2.4.
AppName Optional Application name. For more details, see section 2.2.2.1.
AppVersion Optional Application version. For more details, see section 2.2.2.3.
AppPublisherName Optional Application publisher name. For more details, see section 2.2.2.2. The response message for this operation can result in the following status codes. Status code Description
200 Operation successfully completed.
400 One or more parameters are not valid.
401 Access to the requested resource is denied.
404 The path does not exist.
903.1.1.1.1.1Request Body None.
903.1.1.1.1.2Response Body The response body is a binary stream.
143 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 903.1.1.1.1.3Processing Details 1. The server MUST only respond to requests that have established TLS 1.1 server authentication [RFC4346]. 2. The server MUST retrieve a photo of a certain size, and fill the response body with a binary stream.
903.1.1.2 thumbnail/mediatype/{mediatypedata}/id/{id}/width/ {widthdata}/height/{heightdata} Retrieves the thumbnail of a specified size of the picture, video, and album art of the music. mediatypedata: The media type. See section 2.2.3.24. id: The identifier of the media item. See section 2.2.3.17. widthdata: The desired width of an image. heightdata: The desired height of an image.
HTTP method Description
GET Retrieves the thumbnail of a specified size of the picture, video, and album art of the music.
903.1.1.2.1 GET Retrieves the thumbnail of a specified size of the picture, video, and album art of the music. This operation is transported by an HTTP GET. The operation can be invoked through the following URI:
904 thumbnail/mediatype/{mediatypedata}/id/{id}/width/{widthdata}/height/{heightdata}
The request message for this operation contains the following HTTP headers. Request header Usage Value
Canary Optional The value returned in the logon Response Canary header. Client MUST either pass this header to the server or pass all of the following headers to the server. For more details, see section 2.2.2.5.
Authorization Optional The caller's credential is encoded text that is based on user name and password. For more details, see section 2.2.2.4.
AppName Optional Application name. For more details, see section 2.2.2.1.
AppVersion Optional Application version. For more details, see section 2.2.2.3.
AppPublisherName Optional Application publisher name. For more details, see section 2.2.2.2. The response message for this operation can result in the following status codes. Status code Description
200 Operation successfully completed.
400 One or more parameters are not valid.
401 Access to the requested resource is denied.
404 The path does not exist.
144 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 904.1.1.1.1.1Request Body None.
904.1.1.1.1.2Response Body The response body is a binary stream.
904.1.1.1.1.3Processing Details 1. The server MUST only respond to requests that have established TLS 1.1 server authentication [RFC4346]. 2. The server MUST retrieve the thumbnail of a specified size of the picture, video, and album art of the music, and fill the response body with a binary stream.
904.1.1.2 testdata?sizedata={sizedata} Requests data of a certain size to be sent to the client to help calculate the available bandwidth. sizedata: The size of the test data to be retrieved. See section 2.2.3.41.
HTTP method Description
POST Requests data of a certain size to be sent to the client to help calculate the available bandwidth.
904.1.1.2.1 POST Requests data of a certain size to be sent to the client to help calculate the available bandwidth. This operation is transported by an HTTP POST. The operation can be invoked through the following URI:
905 testdata?sizedata={sizedata}
The request message for this operation contains the following HTTP headers. Request header Usage Value
Canary Optional The value returned in the logon Response Canary header. Client MUST either pass this header to the server or pass all of the following headers to the server. For more details, see section 2.2.2.5.
Authorization Optional The caller's credential is encoded text that is based on user name and password. For more details, see section 2.2.2.4.
AppName Optional Application name. For more details, see section 2.2.2.1.
AppVersion Optional Application version. For more details, see section 2.2.2.3.
AppPublisherName Optional Application publisher name. For more details, see section 2.2.2.2. The response message for this operation can result in the following status codes.
145 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 Status code Description
200 Operation successfully completed.
400 One or more parameters are not valid.
401 Access to the requested resource is denied.
404 The path does not exist.
905.1.1.1.1.1Request Body The request body contains sample data that can be used to calculate the available bandwidth. The request body can be empty.
906
906.1.1.1.1.1Response Body The response body is a binary stream with a certain size specified in the request URI.
906.1.1.1.1.2Processing Details The server MUST only respond to requests that have established TLS 1.1 server authentication [RFC4346]. The server MUST generate a binary stream of a certain size and fill the response body with it.
906.1.1.2 metadata/streams/mediatype/{mediatypedata}/id/{id}/index/ {startingindexdata}/count/{requestedcountdata} Retrieves information about the available streams for an audio or video item. mediatypedata: The media type. See section 2.2.3.24. Only "music" or "video" is valid here. id: The identifier of the media item. See section 2.2.3.17. startingindexdata: The numerical position of the first stream to be retrieved. See section 2.2.3.46. requestedcountdata: The requested number of streams to be retrieved. See section 2.2.3.36.
HTTP method Description
GET Retrieves information about the available streams for an audio or video item.
906.1.1.2.1 GET Retrieves information about the available streams for an audio or video item. This operation is transported by an HTTP GET. The operation can be invoked through the following URI:
907 metadata/streams/mediatype/{mediatypedata}/id/{id}/index/{startingindexdata}/count/ {requestedcountdata}
The request message for this operation contains the following HTTP headers.
146 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 Request header Usage Value
Canary Optional The value returned in the logon Response Canary header. Client MUST either pass this header to the server or pass all of the following headers to the server. For more details, see section 2.2.2.5.
Authorization Optional The caller's credential is encoded text that is based on user name and password. For more details, see section 2.2.2.4.
AppName Optional Application name. For more details, see section 2.2.2.1.
AppVersion Optional Application version. For more details, see section 2.2.2.3.
AppPublisherName Optional Application publisher name. For more details, see section 2.2.2.2. The response message for this operation can result in the following status codes. Status code Description
200 Operation successfully completed.
400 One or more parameters are not valid.
401 Access to the requested resource is denied.
404 The path does not exist.
907.1.1.1.1.1Request Body None.
907.1.1.1.1.2Response Body The response body is encoded in XML format.
908
908.1.1.1.1.1Processing Details The server MUST only respond to requests that have established TLS 1.1 server authentication [RFC4346]. The server MUST construct a response in either Xml or JSON format based on the value of the Accept header or XML if the Accept header was not present. The server MUST retrieve information about the available streams for an audio or video item, and fill the response body with type MetadataStreamResult defined in section 2.2.4.46.
908.1.2 Timer Events None.
908.1.3 Other Local Events None.
147 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 908.2 IStorageManagement Server Details
908.2.1 Abstract Data Model This section describes a conceptual service contract that an implementation maintains to participate in this protocol. The described operations of the service contract are provided to facilitate the explanation of how the protocol behaves. This document does not mandate that implementations adhere to this service contract as long as their external behavior is consistent with how it is described in this document.
908.2.1.1 FolderInfo FolderInfo represents the server folder managed by the server. The FolderInfo data model has a full complex type defined in section 2.2.4.30.
908.2.1.2 StorageDriveInfo StorageDriveInfo represents the drive info of storage server, which can be used to create the server folder managed by the primary server. The StorageDriveInfo data model has a full complex type defined in section 2.2.4.69.
908.2.1.3 StorageServerInfo StorageServerInfo represents the storage server, which can be used to create the server folder managed by the primary server. The StorageServerInfo data model has a full complex type defined in section 2.2.4.70.
908.2.2 Timers None.
908.2.3 Initialization None.
908.2.4 Higher-Layer Triggered Events None.
908.2.5 Message Processing Events and Sequencing Rules
Descri Resource ption servers Retriev es storage servers' informa tion. storagedriveinfo?servername={servername} Retriev es the drives
148 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 Descri Resource ption
informa tion of storage server. serverdrives/index/{index}/count/{count} Retriev es a list of drives on the server. serverfolders/index/{index}/count/{count}?username={username} Retriev es a list of shared folders manage d by the server. serverfolder/create/overwritepermissions/{overwritepermissions}? Creates sharename={sharename}&path={path}&description={description}&servername={servername} a shared folder on specific storage server. serverfolder/{id}/delete/deletecontents/{deletecontents} Remove s or ends the sharing of a shared folder manage d by the server. serverfolder/{id}/rename?newname={newname} Rename s a shared folder manage d by the server. serverfolder/{id}/modify/permission/{permission}? Modifies username={username}&name={name}&description={description} the access permiss ions of a user on a shared folder by specifyi ng a user
149 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 Descri Resource ption
name. serverfolder/{id}/modify/usersid/{usersid}/permission/{permission}? Modifies name={name}&description={description} the access permiss ions of a user on a shared folder by specifyi ng a security identifie r. The responses to all the operations can result in the following status codes. Status code Reason phrase Description
200 OK The operation successfully completed.
401 Unauthorized Access to the requested resource is denied.
400 Bad Request One or more parameters are not valid.
404 Not Found The specific resource does not exist.
403 Forbidden The operation is forbidden.
409 Conflict Server folder with the new path already exists.
908.2.5.1 servers Retrieves the information of the storage servers. HTTP method Description
GET Retrieves the storage servers' information.
908.2.5.1.1 GET Retrieves the storage servers' information. This operation is transported by an HTTP GET. The operation can be invoked through the following URI:
909 https://
The request message for this operation contains the following HTTP headers. Request header Usage Value
Canary Optional The user token. Client MUST either pass this header to the server or pass all of the following headers to the server. For more details, refer to section 2.2.2.5.
Authorization Optional The caller's credential is encoded text that is based on user name and password. For more details, refer to section 2.2.2.4.
AppName Optional The client application name. For more details, refer to section 2.2.2.1.
AppVersion Optional The client application version. For more details, refer to section 2.2.2.3.
150 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 Request header Usage Value
AppPublisherName Optional The client application publisher name. For more details, refer to section 2.2.2.2. The response message for this operation can result in the following status codes. Status code Description
200 Operation successfully completed.
401 Access to the requested resource is denied. This API only supports Administrator calls.
909.1.1.1.1.1Request Body None.
909.1.1.1.1.2Response Body The response body is encoded in either XML or JSON format. The format is controlled by the Accept header defined in section 2.2.2.6.
910
910.1.1.1.1.1Processing Details This call returns the storage server's information (section 2.2.4.20). The server MUST construct a response in either XML or JSON format based on the value of the Accept header (section 2.2.2.6), or in XML format if the Accept header is not present.
910.1.1.2 storagedriveinfo?servername={servername} Retrieves the information about the drives on a specific server. servername: The storage server name. HTTP method Description
GET Retrieves the information about the drives on a specific server.
910.1.1.2.1 GET Retrieves the information about the drives on a specific server. This operation is transported by an HTTP GET. The operation can be invoked through the following URI:
911 https://
The request message for this operation contains the following HTTP headers. Request header Usage Value
Canary Optional The user token. Client MUST either pass this header to the server or pass all of the following headers to the server. For more details, refer to section 2.2.2.5.
Authorization Optional The caller's credential is encoded text that is based on user name and password. For more details, refer to section 2.2.2.4.
AppName Optional The client application name. For more details, refer to section 2.2.2.1.
151 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 Request header Usage Value
AppVersion Optional The client application version. For more details, refer to section 2.2.2.3.
AppPublisherName Optional The client application publisher name. For more details, refer to section 2.2.2.2. The response message for this operation can result in the following status codes. Status code Description
200 Operation successfully completed.
400 One or more parameters are not valid.
401 Access to the requested resource is denied. This API only supports Administrator calls.
404 The specific resource does not exist.
911.1.1.1.1.1Request Body None.
911.1.1.1.1.2Response Body The response body is encoded in either XML or JSON format. The format is controlled by the Accept header defined in section 2.2.2.6.
912
912.1.1.1.1.1Processing Details This call returns the information of drives that belong to a specific storage server (section 2.2.4.19). The server MUST construct a response in either XML or JSON format based on the value of the Accept header (section 2.2.2.6), or in XML format if the Accept header is not present.
912.1.1.2 serverdrives/index/{index}/count/{count} Retrieves the information about the drives on the server. index: The index in the collection to start retrieving data. See section 2.2.3.18. count: The maximum count of items to return. See section 2.2.3.5. HTTP method Description
GET Retrieves the information about the drives on the server.
912.1.1.2.1 GET Retrieves the information about the drives on the server. This operation is transported by an HTTP GET. The operation can be invoked through the following URI:
913 https://
152 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 The request message for this operation contains the following HTTP headers. Request header Usage Value
Canary Optional The user token. Client MUST either pass this header to the server or pass all of the following headers to the server. For more details, refer to section 2.2.2.5.
Authorization Optional The caller's credential is encoded text that is based on user name and password. For more details, refer to section 2.2.2.4.
AppName Optional The client application name. For more details, refer to section 2.2.2.1.
AppVersion Optional The client application version. For more details, refer to section 2.2.2.3.
AppPublisherName Optional The client application publisher name. For more details, refer to section 2.2.2.2. The response message for this operation can result in the following status codes. Status code Description
200 Operation successfully completed.
400 One or more parameters are not valid.
401 Access to the requested resource is denied. This API only supports Administrator calls.
404 The specific resource does not exist.
913.1.1.1.1.1Request Body None.
913.1.1.1.1.2Response Body The response body is encoded in either XML or JSON format. The format is controlled by the Accept header defined in section 2.2.2.6.
914
914.1.1.1.1.1Processing Details This call returns the information about the drives on a specific storage server (section 2.2.4.57). The server MUST construct a response in either XML or JSON format based on the value of the Accept header (section 2.2.2.6), or in XML format if the Accept header is not present.
914.1.1.2 serverfolders/index/{index}/count/{count}?username={username} Retrieves a list of shared folders managed by the server. index: The index in the collection to start retrieving data. See section 2.2.3.18. count: The maximum count of items to return. See section 2.2.3.5. username: The user name is used to query access permission on the folder. It is an optional parameter. If it is not specified, the API returns the current access permissions for the user. See section 2.2.3.51.
HTTP method Description
GET Retrieves a list of shared folders managed by the server.
153 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 914.1.1.2.1 GET This operation retrieves a list of shared folders managed by the server. It is transported by an HTTP GET. The operation can be invoked through the following URI:
915 https://
The request message for this operation contains the following HTTP headers. Request header Usage Value
Canary Optional The user token. Client MUST either pass this header to the server or pass all of the following headers to the server. For more details, refer to section 2.2.2.5.
Authorization Optional The caller's credential is encoded text that is based on user name and password. For more details, refer to section 2.2.2.4.
AppName Optional The client application name. For more details, refer to section 2.2.2.1.
AppVersion Optional The client application version. For more details, refer to section 2.2.2.3.
AppPublisherName Optional The client application publisher name. For more details, refer to section 2.2.2.2. The response message for this operation can result in the following status codes. Status code Description
200 Operation successfully completed.
400 One or more parameters are not valid.
401 Access to the requested resource is denied.
404 The specific resource does not exist.
915.1.1.1.1.1Request Body None.
915.1.1.1.1.2Response Body The response body is encoded in either XML or JSON format. The format is controlled by the Accept header defined in section 2.2.2.6.
916
916.1.1.1.1.1Processing Details This call returns the information about drives on a specific storage server. See section 2.2.4.58. The server MUST construct a response in either XML or JSON format based on the value of the Accept header (section 2.2.2.6), or in XML format if the Accept header is not present.
154 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 916.1.1.2 serverfolder/create/overwritepermissions/{overwritepermissions}? sharename={sharename}&path={path}&description={description}&servernam e={servername} This method creates a shared folder on the specific server. sharename: The name of the shared folder to be created. See section 2.2.3.40. overwritepermissions: This flag indicates whether to overwrite the folder descriptions. See section 2.2.3.31. path: The local path of the folder to share on the specific server. See section 2.2.3.32. description: The description of the shared folder. See section 2.2.3.7. servername: The name of the specific server. This is an optional parameter; if not specified, the server folder will be created on the primary server. See section 2.2.3.38.
This is an optional parameter.
HTTP method Description
POST Creates a shared folder on the specific server.
916.1.1.2.1 POST Creates a shared folder on the specific server. This operation is transported by an HTTP POST. The operation can be invoked through the following URI:
917 https://
The request message for this operation contains the following HTTP headers. Request header Usage Value
Canary Optional The user token. Client MUST either pass this header to the server or pass all of the following headers to the server. For more details, refer to section 2.2.2.5.
Authorization Optional The caller's credential is encoded text that is based on user name and password. For more details, refer to section 2.2.2.4.
AppName Optional The client application name. For more details, refer to section 2.2.2.1.
AppVersion Optional The client application version. For more details, refer to section 2.2.2.3.
AppPublisherName Optional The client application publisher name. For more details, refer to section 2.2.2.2. The response message for this operation can result in the following status codes. Status code Description
200 Operation successfully completed.
400 One or more parameters are not valid.
401 Access to the requested resource is denied. This API only supports Administrator calls.
403 The target share path is invalid.
404 The specific resource does not exist.
155 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 917.1.1.1.1.1Request Body None.
917.1.1.1.1.2Response Body None.
917.1.1.1.1.3Processing Details This call creates a shared folder on the specific server.
917.1.1.2 serverfolder/{id}/delete/deletecontents/{deletecontents} Removes or ends the sharing of a shared folder managed by the server. id: The identifier for the shared folder. See section 2.2.3.17. deletecontents: A flag that indicates whether the contents of the shared folder are deleted when the folder is no longer shared. See section 2.2.3.6.
HTTP method Description
POST Removes or ends the sharing of a shared folder managed by the server.
917.1.1.2.1 POST Removes or ends the sharing of a shared folder managed by the server. This operation is transported by an HTTP POST. The operation can be invoked through the following URI:
918 https://
The request message for this operation contains the following HTTP headers. Request header Usage Value
Canary Optional The user token. Client MUST either pass this header to the server or pass all of the following headers to the server. For more details, refer to section 2.2.2.5.
Authorization Optional The caller's credential is encoded text that is based on user name and password. For more details, refer to section 2.2.2.4.
AppName Optional The client application name. For more details, refer to section 2.2.2.1.
AppVersion Optional The client application version. For more details, refer to section 2.2.2.3.
AppPublisherName Optional The client application publisher name. For more details, refer to section 2.2.2.2. The response message for this operation can result in the following status codes. Status code Description
200 Operation successfully completed.
400 One or more parameters are not valid.
401 Access to the requested resource is denied. This API only supports Administrator calls.
404 The specific resource does not exist.
918.1.1.1.1.1Request Body
156 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 None.
918.1.1.1.1.2Response Body None.
918.1.1.1.1.3Processing Details This call stops the sharing of a shared folder managed by the server, and can delete the contents of the folder.
918.1.1.2 serverfolder/{id}/rename?newname={newname} Rename the specified shared folder that is managed by the server. id: The identifier for the shared folder. See section 2.2.3.17. newname: The new name of the shared folder. See section 2.2.3.26.
HTTP method Description
POST Rename the specified shared folder that is managed by the server.
918.1.1.2.1 POST Rename the specified shared folder that is managed by the server. This operation is transported by an HTTP POST. The operation can be invoked through the following URI:
919 https://
The request message for this operation contains the following HTTP headers. Request header Usage Value
Canary Optional The user token. Client MUST either pass this header to the server or pass all of the following headers to the server. For more details, refer to section 2.2.2.5.
Authorization Optional The caller's credential is encoded text that is based on user name and password. For more details, refer to section 2.2.2.4.
AppName Optional The client application name. For more details, refer to section 2.2.2.1.
AppVersion Optional The client application version. For more details, refer to section 2.2.2.3.
AppPublisherName Optional The client application publisher name. For more details, refer to section 2.2.2.2. The response message for this operation can result in the following status codes. Status code Description
200 Operation successfully completed.
400 One or more parameters are not valid.
401 Access to the requested resource is denied. This API only supports Administrator calls.
404 The specific resource does not exist.
409 The shared folder with new name has existed.
157 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 919.1.1.1.1.1Request Body None.
919.1.1.1.1.2Response Body None.
919.1.1.1.1.3Processing Details This call renames the shared folder.
919.1.1.2 serverfolder/{id}/modify/permission/{permission}? username={username}&name={name}&description={description} Modifies the access permissions of a user on a shared folder by specifying a user name. id: The identifier for the shared folder. See section 2.2.3.17. username: The logon name of a user need set access permission. See section 2.2.3.51. permission: The permission level of specific user. See section 2.2.3.33. name: The name of the shared folder. See section 2.2.3.25. description: The description of the shared folder. See section 2.2.3.7.
HTTP method Description
POST Modifies the access permissions of a user on a shared folder by specifying a user name.
919.1.1.2.1 POST Modifies the access permissions of a user on a shared folder by specifying a user name. This operation is transported by an HTTP POST. The operation can be invoked through the following URI:
920 https://
The request message for this operation contains the following HTTP headers. Request header Usage Value
Canary Optional The user token. Client MUST either pass this header to the server or pass all of the following headers to the server. For more details, refer to section 2.2.2.5.
Authorization Optional The caller's credential is encoded text that is based on user name and password. For more details, refer to section 2.2.2.4.
AppName Optional The client application name. For more details, refer to section 2.2.2.1.
AppVersion Optional The client application version. For more details, refer to section 2.2.2.3.
AppPublisherName Optional The client application publisher name. For more details, refer to section 2.2.2.2. The response message for this operation can result in the following status codes.
158 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 Status code Description
200 Operation successfully completed.
400 Operation successfully completed.
401 Access to the requested resource is denied. This API only supports Administrator calls.
404 The specific resource does not exist.
920.1.1.1.1.1Request Body None.
920.1.1.1.1.2Response Body None.
920.1.1.1.1.3Processing Details This call modifies the user access permission on the specific shared folder. The user access permission MAY also be affected by access permission settings of the user group.
920.1.1.2 serverfolder/{id}/modify/usersid/{usersid}/permission/{permission}? name={name}&description={description} Modifies the access permissions of a user on a shared folder by specifying a security identifier. id: The identifier for the shared folder. See section 2.2.3.17. usersid: The security identifier (SID) of a user. See section 2.2.3.52. permission: The permission level of specific user. See section 2.2.3.33. name: The name of the shared folder. See section 2.2.3.25. description: The description of the shared folder. See section 2.2.3.7.
HTTP method Description
POST Modifies the access permissions of a user on a shared folder by specifying a security identifier.
920.1.1.2.1 POST Modifies the access permissions of a user on a shared folder by specifying a security identifier. This operation is transported by an HTTP POST. The operation can be invoked through the following URI:
921 https://
The request message for this operation contains the following HTTP headers. Request header Usage Value
Canary Optional The user token. Client MUST either pass this header to the server or pass all of
159 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 Request header Usage Value
the following headers to the server. For more details, refer to section 2.2.2.5.
Authorization Optional The caller's credential is encoded text that is based on user name and password. For more details, refer to section 2.2.2.4.
AppName Optional The client application name. For more details, refer to section 2.2.2.1.
AppVersion Optional The client application version. For more details, refer to section 2.2.2.3
AppPublisherName Optional The client application publisher name. For more details, refer to section 2.2.2.2. The response message for this operation can result in the following status codes. Status code Description
200 Operation successfully completed.
400 One or more parameters are not valid.
401 Access to the requested resource is denied. This API only supports Administrator calls.
404 The specific resource does not exist.
921.1.1.1.1.1Request Body None.
921.1.1.1.1.2Response Body None.
921.1.1.1.1.3Processing Details This call modifies the user access permission on the specific shared folder. The user access permission MAY also be affected by access permission settings of the user group.
921.1.2 Timer Events None.
921.1.3 Other Local Events None.
921.2 IUserManagement Server Details
921.2.1 Abstract Data Model This section describes a conceptual service contract that an implementation maintains to participate in this protocol. The described operations of the service contract are provided to facilitate the explanation of how the protocol behaves. This document does not mandate that implementations adhere to this service contract as long as their external behavior is consistent with how it is described in this document.
160 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 921.2.1.1 UserInfo The UserInfo represents the information of a user. The UserInfo data model has a full complex type defined in section 2.2.4.71.
921.2.2 Timers None.
921.2.3 Initialization None.
921.2.4 Higher-Layer Triggered Events None.
921.2.5 Message Processing Events and Sequencing Rules
Descri Resource ption users/index/{startingindex}/count/{amount} Retriev es a list of users that have been created on the server. usergroups Retriev es a list of groups that have been created on the server. users/connection/index/{startingindex}/count/{amount}?username={username} Retriev es the connec tion informa tion for a specific user. user/{userid}/enable Activat es a user based on a specifie d securit y identifi er.
161 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 Descri Resource ption user/{userid}/disable Deactiv ates a user in the domain . user/setpassword/{userid} Change s the passwo rd of a domain user. user/{id}/update? Update firstname={firstname}&lastname={lastname}&remotewebaccess={remotewebaccess}&vpnaccess={v s user pnaccess} informa tion and permis sions. usergroup/{groupguid}/addusers Add users to a specific group. usergroup/{groupguid}/removeusers Remov es users from a specific group. user/add? Creates username={username}&firstname={firstname}&lastname={lastname}&remotewebaccess={remotewe a new baccess}&vpnaccess={vpnaccess}&usergroups={usergroups} standar d user on the domain . user/{id}/delete Remov es a standar d user. The responses to all the operations can result in the following status codes. Status code Reason phrase Description
200 OK Operation successfully completed.
400 Bad Request One or more parameters are not valid.
401 Unauthorized Access to the requested resource is denied.
404 Not Found The specific resource does not exist.
403 Forbidden Operation is forbidden.
921.2.5.1 users/index/{startingindex}/count/{amount} Retrieves a list of users that have been created on the server's Active Directory.
162 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 startingindex: The numerical position of the first user to be retrieved. See section 2.2.3.45. amount: The number of users to be retrieved. See section 2.2.3.2.
HTTP method Description
GET Retrieves a list of users that have been created on the Active Directory.
921.2.5.1.1 GET Retrieves a list of users that have been created on the AD DS server. This operation is transported by an HTTP GET. The operation can be invoked through the following URI:
922 https://
The request message for this operation contains the following HTTP headers. Request header Usage Value
Canary Optional The user token. Client MUST either pass this header to the server or pass all of the following headers to the server. For more details, refer to section 2.2.2.5.
Authorization Optional The caller's credential is encoded text that is based on user name and password. For more details, refer to section 2.2.2.4.
AppName Optional The client application name. For more details, refer to section 2.2.2.1.
AppVersion Optional The client application version. For more details, refer to section 2.2.2.3.
AppPublisherName Optional The client application publisher name. For more details, refer to section 2.2.2.2. The response message for this operation can result in the following status codes. Status code Description
200 Operation successfully completed.
400 One or more parameters are not valid.
401 Access to the requested resource is denied. This API only supports Administrator calls. For more detail on the UserInfo type, please see section 2.2.4.71.
922.1.1.1.1.1Request Body None.
922.1.1.1.1.2Response Body The response body is encoded in either XML or JSON format. The format is controlled by the Accept header defined in section 2.2.2.6.
923
923.1.1.1.1.1Processing Details This call returns the information of users that were created on the AD DS server. See section 2.2.4.71.
163 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 The server MUST construct a response in either XML or JSON format based on the value of the Accept header (section 2.2.2.6), or in XML format if the Accept header is not present.
923.1.1.2 usergroups Retrieves a list of groups that have been created on the server's Active Directory. HTTP method Description
GET Retrieves a list of groups that have been created on the server.
923.1.1.2.1 GET Retrieves a list of groups that have been created on the server. This operation is transported by an HTTP GET. The operation can be invoked through the following URI:
924 https://
The request message for this operation contains the following HTTP headers. Request header Usage Value
Canary Optional The user token. Client MUST either pass this header to the server or pass all of the following headers to the server. For more details, refer to section 2.2.2.5.
Authorization Optional The caller's credential is encoded text that is based on user name and password. For more details, refer to section 2.2.2.4.
AppName Optional The client application name. For more details, refer to section 2.2.2.1.
AppVersion Optional The client application version. For more details, refer to section 2.2.2.3.
AppPublisherName Optional The client application publisher name. For more details, refer to section 2.2.2.2. The response message for this operation can result in the following status codes. Status code Description
200 Operation successfully completed.
401 Access to the requested resource is denied. This API only supports Administrator calls.
924.1.1.1.1.1Request Body None.
924.1.1.1.1.2Response Body The response body is encoded in XML format.
925
925.1.1.1.1.1Processing Details This call returns the information about groups created on the AD DS server. See section 2.2.4.31.
164 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 The server MUST construct a response in either XML or JSON format based on the value of the Accept header (section 2.2.2.6), or in XML format if the Accept header is not present.
925.1.1.2 users/connection/index/{startingindex}/count/{amount}? username={username} Retrieves the connection information related to a specific user. startingindex: The numerical position of the first user to be retrieved. See section 2.2.3.45. amount: The number of items to be retrieved. See section 2.2.3.2. username: The user name of a specific user. It is an optional parameter; if the caller doesn’t specify this parameter, the API returns all of the user's connection information.
HTTP method Description
GET Retrieves the connection information related to a specific user.
925.1.1.2.1 GET Retrieves the connection information related to a specific user. This operation is transported by an HTTP GET. The operation can be invoked through the following URI:
926 https://
The request message for this operation contains the following HTTP headers. Request header Usage Value
Canary Optional The user token. Client MUST either pass this header to the server or pass all of the following headers to the server. For more details, refer to section 2.2.2.5.
Authorization Optional The caller's credential is encoded text that is based on user name and password. For more details, refer to section 2.2.2.4.
AppName Optional The client application name. For more details, refer to section 2.2.2.1.
AppVersion Optional The client application version. For more details, refer to section 2.2.2.3.
AppPublisherName Optional The client application publisher name. For more details, refer to section 2.2.2.2. The response message for this operation can result in the following status codes. Status code Description
200 Operation successfully completed.
400 One or more parameters are not valid.
401 Access to the requested resource is denied. This API only supports Administrator calls.
404 The specific resource does not exist.
926.1.1.1.1.1Request Body None.
165 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 926.1.1.1.1.2Response Body The response body is encoded in either XML or JSON format. The format is controlled by the Accept header defined in section 2.2.2.6.
927
927.1.1.1.1.1Processing Details This call returns the connection information of a specific user. See section 2.2.4.26. The server MUST construct a response in either XML or JSON format based on the value of the Accept header (section 2.2.2.6), or in XML format if the Accept header is not present.
927.1.1.2 user/{userid}/enable Activates a user based on a specified security identifier. userid: The ID of the user; it is recommended to be the security identifier of the user. See section 2.2.3.50.
HTTP method Description
POST Activates a user based on a specified security identifier.
927.1.1.2.1 POST Activates a user based on a specified security identifier. This operation is transported by an HTTP POST. The operation can be invoked through the following URI:
928 https://
The request message for this operation contains the following HTTP headers. Request header Usage Value
Canary Optional The user token. Client MUST either pass this header to the server or pass all of the following headers to the server. For more details, refer to section 2.2.2.5.
Authorization Optional The caller's credential is encoded text that is based on user name and password. For more details, refer to section 2.2.2.4.
AppName Optional The client application name. For more details, refer to section 2.2.2.1.
AppVersion Optional The client application version. For more details, refer to section 2.2.2.3.
AppPublisherName Optional The client application publisher name. For more details, refer to section 2.2.2.2. The response message for this operation can result in the following status codes. Status code Description
200 Operation successfully completed.
400 One or more parameters are not valid.
401 Access to the requested resource is denied. This API only supports Administrator calls.
404 The specific resource does not exist.
166 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 928.1.1.1.1.1Request Body None.
928.1.1.1.1.2Response Body None.
928.1.1.1.1.3Processing Details This call actives the user specified by userid.
928.1.1.2 user/{userid}/disable Deactivates a user in the domain. userid: The SID of the user. See section 2.2.3.50.
HTTP method Description
POST Deactivates a user in the domain.
928.1.1.2.1 POST Deactivates a user in the domain. This operation is transported by an HTTP POST. The operation can be invoked through the following URI:
929 https://
The request message for this operation contains the following HTTP headers. Request header Usage Value
Canary Optional The user token. Client MUST either pass this header to the server or pass all of the following headers to the server. For more details, refer to section 2.2.2.5.
Authorization Optional The caller's credential is encoded text that is based on user name and password. For more details, refer to section 2.2.2.4.
AppName Optional The client application name. For more details, refer to section 2.2.2.1.
AppVersion Optional The client application version. For more details, refer to section 2.2.2.3.
AppPublisherName Optional The client application publisher name. For more details, refer to section 2.2.2.2. The response message for this operation can result in the following status codes. Status code Description
200 Operation successfully completed.
400 One or more parameters are not valid.
401 Access to the requested resource is denied. This API only supports Administrator calls.
404 The specific resource does not exist.
929.1.1.1.1.1Request Body
167 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 None.
929.1.1.1.1.2Response Body None.
929.1.1.1.1.3Processing Details This call disables the user specified by the user ID (userid).
929.1.1.2 user/setpassword/{userid} Changes the password of a domain user. userid: The ID of the user; it is recommended to be the security identifier of the user. See section 2.2.3.50.
HTTP method Description
POST Changes the password of a domain user.
929.1.1.2.1 POST Changes the password of a domain user. This operation is transported by an HTTP POST. The operation can be invoked through the following URI:
930 https://
The request message for this operation contains the following HTTP headers. Request header Usage Value
Canary Optional The user token. Client MUST either pass this header to the server or pass all of the following headers to the server. For more details, refer to section 2.2.2.5.
Authorization Optional The caller's credential is encoded text that is based on user name and password. For more details, refer to section 2.2.2.4.
AppName Optional The client application name. For more details, refer to section 2.2.2.1.
AppVersion Optional The client application version. For more details, refer to section 2.2.2.3.
AppPublisherName Optional The client application publisher name. For more details, refer to section 2.2.2.2. The response message for this operation can result in the following status codes. Status code Description
200 Operation successfully completed.
400 One or more parameters are not valid.
401 Access to the requested resource is denied. This API only supports Administrator calls.
404 The specific resource does not exist.
930.1.1.1.1.1Request Body
168 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 The request body is encoded in XML format or JSON format based on the value of the Accept header (section 2.2.2.6), or in XML format if the Accept header is not present.
930.1.1.1.1.2Response Body None.
930.1.1.1.1.3Processing Details This call changes the password of the user specified by the user ID (userid). The new password MUST be specified in the body of the request, in the text of the string element.
930.1.1.2 user/{id}/update? firstname={firstname}&lastname={lastname}&remotewebaccess={remoteweb access}&vpnaccess={vpnaccess} Updates user information and permissions. id: The SID of a user. See section 2.2.3.17. firstname: The first name of the user. See section 2.2.3.12. lastname: The last name of the user. See section 2.2.3.22. remotewebaccess: A flag indicates whether the user has remote web access permission. See section 2.2.3.35. vpnaccess: A flag indicates whether the user has vpn access permission. See section 2.2.3.53.
HTTP method Description
POST Updates user information and permissions.
930.1.1.2.1 POST This operation updates user information and permissions. It is transported by an HTTP POST. The operation can be invoked through the following URI:
931 https://
The request message for this operation contains the following HTTP headers. Request header Usage Value
Canary Optional The user token. Client MUST either pass this header to the server or pass all of the following headers to the server. For more details, refer to section 2.2.2.5.
Authorization Optional The caller's credential is encoded text that is based on user name and password. For more details, refer to section 2.2.2.4.
AppName Optional The client application name. For more details, refer to section 2.2.2.1.
AppVersion Optional The client application version. For more details, refer to section 2.2.2.3.
AppPublisherName Optional The client application publisher name. For more details, refer to section 2.2.2.2.
169 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 The response message for this operation can result in the following status codes. Status code Description
200 Operation successfully completed.
400 One or more parameters are not valid.
401 Access to the requested resource is denied. This API only supports Administrator calls.
404 The specific resource does not exist.
931.1.1.1.1.1Request Body None.
931.1.1.1.1.2Response Body None.
931.1.1.1.1.3Processing Details This call updates the specified user information and permissions.
931.1.1.2 usergroup/{groupguid}/addusers Adds users to the specified user group. groupguid: The GUID of the group. See section 2.2.3.13.
HTTP method Description
POST Adds users to the specified user group.
931.1.1.2.1 POST Adds users to the specified user group. This operation is transported by an HTTP POST. The operation can be invoked through the following URI:
932 https://
The request message for this operation contains the following HTTP headers. Request header Usage Value
Canary Optional The user token. Client MUST either pass this header to the server or pass all of the following headers to the server. For more details, refer to section 2.2.2.5.
Authorization Optional The caller's credential is encoded text that is based on user name and password. For more details, refer to section 2.2.2.4.
AppName Optional The client application name. For more details, refer to section 2.2.2.1.
AppVersion Optional The client application version. For more details, refer to section 2.2.2.3.
AppPublisherName Optional The client application publisher name. For more details, refer to section 2.2.2.2. The response message for this operation can result in the following status codes.
170 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 Status code Description
200 Operation successfully completed.
400 One or more parameters are not valid.
401 Access to the requested resource is denied. This API only supports Administrator calls.
404 The specific resource does not exist.
932.1.1.1.1.1Request Body The request body is encoded in XML format or JSON format based on the value of the Accept header (section 2.2.2.6), or in XML format if the Accept header is not present.
932.1.1.1.1.2Response Body None.
932.1.1.1.1.3Processing Details This call will add the users specified by the GUIDs in the request body to the group specified by GroupGuid.
932.1.1.2 usergroup/{groupguid}/removeusers Removes users from the specified user group. groupguid: The GUID of the group. See section 2.2.3.13.
HTTP method Description
POST Removes users from the specified user group.
932.1.1.2.1 POST Removes users from the specified user group. This operation is transported by an HTTP POST. The operation can be invoked through the following URI:
933 https://
The request message for this operation contains the following HTTP headers. Request header Usage Value
Canary Optional The user token. Client MUST either pass this header to the server or pass all of the following headers to the server. For more details, refer to section 2.2.2.5.
Authorization Optional The caller's credential is encoded text that is based on user name and password. For more details, refer to section 2.2.2.4.
AppName Optional The client application name. For more details, refer to section 2.2.2.1.
AppVersion Optional The client application version. For more details, refer to section 2.2.2.3.
AppPublisherName Optional The client application publisher name. For more details, refer to section 2.2.2.2. The response message for this operation can result in the following status codes.
171 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 Status code Description
200 Operation successfully completed.
400 One or more parameters are not valid.
401 Access to the requested resource is denied. This API only supports Administrator calls.
404 The specific resource does not exist.
933.1.1.1.1.1Request Body The request body is encoded in XML format or JSON format based on the value of the Accept header (section 2.2.2.6), or in XML format if the Accept header is not present.
933.1.1.1.1.2Response Body None.
933.1.1.1.1.3Processing Details This call removes the users specified by the GUIDs in the request body from the group specified by GroupGuid.
933.1.1.2 user/add? username={username}&firstname={firstname}&lastname={lastname}&remot ewebaccess={remotewebaccess}&vpnaccess={vpnaccess}&usergroups={user groups} Creates a new standard user on the domain. username: The name of the user. It SHOULD be the logon name of the user. See section 2.2.3.51. firstname: The first name of the user. See section 2.2.3.12. lastname: The last name of the user. See section 2.2.3.22. remotewebaccess: A flag indicating whether the user has remote web access permission. See section 2.2.3.35. vpnaccess: A flag indicating whether the user has vpn access permission. See section 2.2.3.53. usergroups: A comma-separated list of group GUIDs. It is an optional parameter<13>. See section 2.2.3.49.
HTTP method Description
POST Creates a new standard user on the domain.
933.1.1.2.1 POST Creates a new standard user on the domain. This operation is transported by an HTTP POST. The operation can be invoked through the following URI:
934 https://
172 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 The request message for this operation contains the following HTTP headers. Request header Usage Value
Canary Optional The user token. Client MUST either pass this header to the server or pass all of the following headers to the server. For more details, refer to section 2.2.2.5.
Authorization Optional The caller's credential is encoded text that is based on user name and password. For more details, refer to section 2.2.2.4.
AppName Optional The client application name. For more details, refer to section 2.2.2.1.
AppVersion Optional The client application version. For more details, refer to section 2.2.2.3.
AppPublisherName Optional The client application publisher name. For more details, refer to section 2.2.2.2. The response message for this operation can result in the following status codes. Status code Description
200 Operation successfully completed.
400 One or more parameters are not valid.
401 Access to the requested resource is denied. This API only supports Administrator calls.
403 A user with the requested name already exists.
404 The specific resource does not exist.
934.1.1.1.1.1Request Body The request body is encoded in XML format or JSON format based on the value of the Accept header (section 2.2.2.6), or in XML format if the Accept header is not present.
934.1.1.1.1.2Response Body None.
934.1.1.1.1.3Processing Details This call creates a standard user with specified user information and permission settings. A user with domain administrator permission cannot be created with this method.
934.1.1.2 user/{id}/delete Removes a standard user. id: The security identifier (SID) of a user.
HTTP method Description
POST Removes a standard user.
934.1.1.2.1 POST This operation removes a standard user and is transported by an HTTP POST. The operation can be invoked through the following URI:
173 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 935 https://
The request message for this operation contains the following HTTP headers. Request header Usage Value
Canary Optional The user token. Client MUST either pass this header to the server or pass all of the following headers to the server. For more details, refer to section 2.2.2.5.
Authorization Optional The caller's credential is encoded text that is based on user name and password. For more details, refer to section 2.2.2.4.
AppName Optional The client application name. For more details, refer to section 2.2.2.1.
AppVersion Optional The client application version. For more details, refer to section 2.2.2.3.
AppPublisherName Optional The client application publisher name. For more details, refer to section 2.2.2.2. The response message for this operation can result in the following status codes. Status code Description
200 Operation successfully completed.
400 One or more parameters are not valid.
401 Access to the requested resource is denied. This API only supports Administrator calls.
404 The specific resource does not exist.
935.1.1.1.1.1Request Body None.
935.1.1.1.1.2Response Body None.
935.1.1.1.1.3Processing Details This call removes the user specified by id.
935.1.2 Timer Events None.
935.1.3 Other Local Events None.
935.2 ISharePointSiteMgmt Server Details
935.2.1 Abstract Data Model None.
935.2.2 Timers None.
174 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 935.2.3 Initialization None.
935.2.4 Higher-Layer Triggered Events None.
935.2.5 Message Processing Events and Sequencing Rules
Resource Description site Retrieves the team site and my site URI.
935.2.5.1 site
HTTP method Description
GET Retrieves the team site and my site URI.
935.2.5.1.1 GET Retrieves the team site and my site URI. This operation is transported by an HTTP GET. The operation can be invoked through the following URI:
936 https://
The request message for this operation contains the following HTTP headers. Request header Usage Value
Canary Optional The user token. Client MUST either pass this header to the server or pass all of the following headers to the server. For more details, refer to section 2.2.2.5.
Authorization Optional The caller's credential is encoded text that is based on user name and password. For more details, refer to section 2.2.2.4.
AppName Optional The client application name. For more details, refer to section 2.2.2.1.
AppVersion Optional The client application version. For more details, refer to section 2.2.2.3.
AppPublisherName Optional The client application publisher name. For more details, refer to section 2.2.2.2.
936.1.1.1.1.1Request Body The request body is encoded in XML format.
936.1.1.1.1.2Response Body The response body is encoded in XML format.
937
937.1.1.1.1.1Processing Details This call returns information about the SharePoint site. See section 2.2.4.68.
175 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 The server MUST construct a response in either XML or JSON format based on the value of the Accept header (section 2.2.2.6), or in XML format if the Accept header is not present.
937.1.2 Timer Events None.
937.1.3 Other Local Events None.
937.2 IWindowsPhoneManagement Server Details
937.2.1 Abstract Data Model None.
937.2.2 Timers None.
937.2.3 Initialization None.
937.2.4 Higher-Layer Triggered Events None.
937.2.5 Message Processing Events and Sequencing Rules
Resource Description
/notification/subscribe?deviceid={deviceid} Registers or updates registration for a device to receive Windows phone tile updates notifications.
/notification/unsubscribe?deviceid={deviceid} Unsubscribes a device from Windows phone tile updates. The responses to all the operations can result in the following status codes. Status code Reason phrase Description
200 OK Operation successfully completed.
400 Bad Request One or more parameters are not valid.
401 Unauthorized Access to the requested resource is denied.
404 Not Found The specific resource does not exist.
937.2.5.1 /notification/subscribe?deviceid={deviceid} Registers or updates the registration for a device to receive Windows Phone tile updates notifications. deviceid: The ID of the device.
176 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 HTTP method Description
POST Registers or updates the registration for a device to receive Windows Phone tile updates notifications.
937.2.5.1.1 POST Registers or updates the registration for a device to receive Windows Phone tile updates notifications. This operation is transported by an HTTP POST. The operation can be invoked through the following URI:
938 https://
The request message for this operation contains the following HTTP headers. Request header Usage Value
Canary Optional The user token. Client MUST either pass this header to the server or pass all of the following headers to the server. For more details, refer to section 2.2.2.5.
Authorization Optional The caller's credential is encoded text that is based on user name and password. For more details, refer to section 2.2.2.4.
AppName Optional The client application name. For more details, refer to section 2.2.2.1.
AppVersion Optional The client application version. For more details, refer to section 2.2.2.3.
AppPublisherName Optional The client application publisher name. For more details, refer to section 2.2.2.2. The response message for this operation can result in the following status codes. Status code Description
200 Operation successfully completed.
400 One or more parameters are not valid.
401 Access to the requested resource is denied.
938.1.1.1.1.1Request Body The request body is encoded in XML format or JSON format based on the value of the Accept header (section 2.2.2.6), or in XML format if the Accept header is not present. The request content is the push notification channel URI obtained from the Microsoft Push Notification Service.
938.1.1.1.1.2Response Body None.
938.1.1.1.1.3Processing Details This call removes the user specified by the ID.
177 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 938.1.1.2 /notification/unsubscribe?deviceid={deviceid} Unsubscribes a device from the Windows Phone tile updates. deviceid: The ID of the device.
HTTP method Description
POST Unsubscribes a device from Windows Phone tile updates.
938.1.1.2.1 POST Unsubscribes a device from Windows Phone tile updates. This operation is transported by an HTTP POST. The operation can be invoked through the following URI:
939 https://
The request message for this operation contains the following HTTP headers. Request header Usage Value
Canary Optional The user token. Client MUST either pass this header to the server or pass all of the following headers to the server. For more details, refer to section 2.2.2.5.
Authorization Optional The caller's credential is encoded text that is based on user name and password. For more details, refer to section 2.2.2.4.
AppName Optional The client application name. For more details, refer to section 2.2.2.1.
AppVersion Optional The client application version. For more details, refer to section 2.2.2.3.
AppPublisherName Optional The client application publisher name. For more details, refer to section 2.2.2.2. The response message for this operation can result in the following status codes. Status code Description
200 Operation successfully completed.
400 One or more parameters are not valid.
401 Access to the requested resource is denied.
404 The device specified by the device ID is not registered.
939.1.1.1.1.1Request Body None.
939.1.1.1.1.2Response Body None.
939.1.1.1.1.3Processing Details This call unsubscribes a device from Windows Phone tile updates.
939.1.2 Timer Events None.
178 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 939.1.3 Other Local Events None.
179 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 940 Protocol Examples
940.1 Login Client Request:
941 GET https://www.contoso.com/services/builtin/session.svc/login HTTP/1.1
942 User-Agent: Sample App Name/1.0.0.0
943 Accept: application/xml
944 AppName: Sample App Name
945 AppVersion: 1.0.0.0
946 AppPublisherName: Publisher
947 Authorization: Basic VXNlcjpQYXNzd29yZCE=
948 Host: domainName
Server Response (XML):
949 HTTP/1.1 200 OK
950 Cache-Control: no-cache
951 Server: Microsoft-IIS/8.5
952 Set-Cookie: ASP.NET_SessionId=hincf5pfrry4etux3rfe4n5k; path=/; HttpOnly
953 Canary: 7a10f945-91af-0597-14fd-a03bbdec2420
954 X-AspNet-Version: 4.0.30319
955 X-Powered-By: ASP.NET
956 X-Content-Type-Options: nosniff
957 Date: Fri, 14 Jun 2013 10:56:44 GMT
958 Content-Length: 0
958.1 Get Server Information Client Request:
959 GET https://www.contoso.com/services/builtin/servermanagement.svc/serverinformation HTTP/1.1
960 User-Agent: Sample App Name/1.0.0.0
961 Accept: application/xml
962 AppName: Sample App Name
963 AppVersion: 1.0.0.0
180 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 964 AppPublisherName: Publisher
965 Authorization: Basic VXNlcjpQYXNzd29yZCE=
966 Host: domainName
Server Response (XML):
967 HTTP/1.1 200 OK
968 Cache-Control: no-cache
969 Content-Length: 633
970 Content-Type: application/xml; charset=utf-8
971 Server: Microsoft-IIS/8.5
972 X-AspNet-Version: 4.0.30319
973 X-Powered-By: ASP.NET
974 X-Content-Type-Options: nosniff
975 Date: Fri, 14 Jun 2013 10:56:44 GMT
976
977
978
979
980
981
982
983
984
985
986
986.1 Get Server Folders Client Request:
987 GET https://www.contoso.com/services/builtin/storagemanagement.svc/serverfolders/index/0/count/2 147483647 HTTP/1.1
988 User-Agent: Sample App Name/1.0.0.0
181 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 989 Accept: application/xml
990 Canary: 7a10f945-91af-0597-14fd-a03bbdec2420
991 Host: domainName
992 Cookie: ASP.NET_SessionId=hincf5pfrry4etux3rfe4n5k
993 Host: domainName
Server Response (XML):
994 HTTP/1.1 200 OK
995 Cache-Control: no-cache
996 Content-Length: 1791
997 Content-Type: application/xml; charset=utf-8
998 Server: Microsoft-IIS/8.5
999 X-AspNet-Version: 4.0.30319
1000 X-Powered-By: ASP.NET
1001 X-Content-Type-Options: nosniff
1002 Date: Fri, 14 Jun 2013 11:08:10 GMT
1003
1004
1005
1006
1007
1008
1009
1010
1011
1012
1013
1014
1015
1016
182 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 1017
1018
1019
1020
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040
1041
1042
1043
1044
1045
183 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 1046
1047
1048
1049
1050
1050.1 Retrieve the Metadata for Items within a Folder Client Request:
1051 GET https://www.contoso.com/services/builtin/fileoperationservice.svc/items/index/0/count/510? path=%5C%5CdomainName%5CCompany&filter=All&sortByField=Name&ascending=True HTTP/1.1
1052 User-Agent: Sample App Name/1.0.0.0
1053 Accept: application/xml
1054 Canary: 7a10f945-91af-0597-14fd-a03bbdec2420
1055 Host: domainName
1056 Cookie: ASP.NET_SessionId=hincf5pfrry4etux3rfe4n5k
Server Response (XML):
1057 HTTP/1.1 200 OK
1058 Cache-Control: no-cache
1059 Content-Length: 1173
1060 Content-Type: application/xml; charset=utf-8
1061 Server: Microsoft-IIS/8.5
1062 X-AspNet-Version: 4.0.30319
1063 X-Powered-By: ASP.NET
1064 X-Content-Type-Options: nosniff
1065 Date: Mon, 02 Dec 2013 03:46:55 GMT
1066
1067
1068
1069
1070
184 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 1071
1072
1073
1074
1075
1076
1077
1078
1079
1080
1081
1082
1083
1084
1085
1086
1087
1088
1089
1090
1091
1092
1093
1094
1095
1096
1097
1098
1099
185 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 1100
1101
1102
1103
1104
1105
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116
1117
1118
1119
1120
1121
1122
1123
1124
1125
1126
1127
1128
186 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 1129
1130
1131
1132
1133
1134
1135
1136
1136.1 Create a Folder Client Request:
1137 POST https://www.contoso.com/services/builtin/fileoperationservice.svc/folder?path= %5C%5CDomainName%5CCompany%5CDemo+Folder HTTP/1.1
1138 User-Agent: Sample App Name/1.0.0.0
1139 Accept: application/xml
1140 Canary: 7a10f945-91af-0597-14fd-a03bbdec2420
1141 Host: DomainName
1142 Cookie: ASP.NET_SessionId=hincf5pfrry4etux3rfe4n5k
1143 Content-Length: 0
Server Response (XML):
1144 HTTP/1.1 201 Created
1145 Cache-Control: no-cache
1146 Server: Microsoft-IIS/8.5
1147 X-AspNet-Version: 4.0.30319
1148 X-Powered-By: ASP.NET
1149 X-Content-Type-Options: nosniff
1150 Date: Fri, 14 Jun 2013 11:35:21 GMT
1151 Content-Length: 0
1151.1 Upload a File Client Request:
187 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 1152 POST https://www.contoso.com/services/builtin/filecontentaccessservice.svc/filecontent?path=%5C %5CDomainName%5CCompany%5CDemo+Folder%5Ctext.txt&overwrite=True HTTP/1.1
1153 Accept: */*
1154 AppName: Sample App Name
1155 AppVersion: 1.0.0.0
1156 AppPublisherName: Publisher
1157 Authorization: Basic VXNlcjpQYXNzd29yZCE=
1158 UA-CPU: AMD64
1159 Accept-Encoding: gzip, deflate
1160 User-Agent: Mozilla/5.0 (compatible; MSIE 10.0; Windows NT 6.2; Win64; x64; Trident/6.0)
1161 Host: DomainName
1162 Content-Length: 24
1163 Connection: Keep-Alive
1164 Cache-Control: no-cache
1165
Server Response (XML):
1166 HTTP/1.1 201 Created
1167 Cache-Control: no-cache
1168 Server: Microsoft-IIS/8.5
1169 X-AspNet-Version: 4.0.30319
1170 X-Powered-By: ASP.NET
1171 X-Content-Type-Options: nosniff
1172 Date: Fri, 14 Jun 2013 11:38:19 GMT
1173 Content-Length: 0
1173.1 Logout Client Request:
1174 GET https://www.contoso.com/services/builtin/session.svc/logout HTTP/1.1
1175 User-Agent: MSampleAppName/1.0.0.0
1176 Accept: application/xml
1177 Canary: 7a10f945-91af-0597-14fd-a03bbdec2420
188 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 1178 Host: domainName
1179 Cookie: ASP.NET_SessionId=hincf5pfrry4etux3rfe4n5k
Server Response (XML):
1180 HTTP/1.1 200 OK
1181 Cache-Control: no-cache
1182 Server: Microsoft-IIS/8.5
1183 X-AspNet-Version: 4.0.30319
1184 Set-Cookie: ASP.NET_SessionId=; path=/
1185 X-Powered-By: ASP.NET
1186 X-Content-Type-Options: nosniff
1187 Date: Fri, 14 Jun 2013 11:47:07 GMT
1188 Content-Length: 0
189 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 1189 Security
1189.1 Security Considerations for Implementers The Server and File Management Web APIs Protocol requires that all requests except GetCustomizationInfo (see section 3.10.5.1.1) from the client be authenticated. The client is expected to submit requests with user credential headers or use an implementation-dependent authentication mechanism to obtain a security token and include that token in the HTTP Canary header. The server will validate the user credential information or security token and use it to authorize the request.
1189.2 Index of Security Parameters None.
190 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 1190 Appendix A: Full WSDL
1191
1192
1193
1194
1195
1196
1197
1198
1199
1200
1201
1202
1203
1204
1205
1206
1207
191 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 1208
1209
1210
1211
1212
1213
1214
1215
1216
1217
1218
1219
1220
1221
1222
1223
1224
1225
1226
1227
1228
1229
1230
1231
1232
1233
1234
1235
1236
192 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 1237
1238
1239
1240
1241
1242
1243
1244
1245
1246
1247
1248
1249
1250
1251
1252
1253
1254
1255
1256
1257
1258
1259
1260
1261
1262
1263
1264
1265
193 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 1266
1267
1268
1269
1270
1271
1272
1273
1274
1275
1276
1277
1278
1279
1280
1281
1282
1283
1284
1285
1286
1287
1288
1289
1290
1291
1292
1293
1294
194 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 1295
1296
1297
1298
1299
1300
1301
1302
1303
1304
1305
1306
1307
1308
1309
1310
1311
1312
1313
1314
1315
1316
1317
1318
1319
1320
1321
1322
1323
195 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 1324
1325
1326
1327
1328
1329
1330
1331
1332
1333
1334
1335
1336
1337
1338
1339
1340
1341
1342
1343
1344
1345
1346
1347
1348
1349
1350
1351
1352
196 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 1353
1354
1355
1356
1357
1358
1359
1360
1361
1362
1363
1364
1365
1366
1367
1368
1369
1370
1371
1372
1373
1374
1375
1376
1377
1378
1379
1380
1381
197 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 1382
1383
1384
1385
1386
1387
1388
1389
1390
1391
1392
1393
1394
1395
1396
1397
1398
1399
1400
1401
1402
1403
1404
1405
1406
1407
1408
1409
1410
198 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 1411
1412
1413
1414
1415
1416
1417
1418
1419
1420
1421
1422
1423
1424
1425
1426
1427
1428
1429
1430
1431
1432
1433
1434
1435
1436
1437
1438
1439
199 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 1440
1441
1442
1443
1444
1445
1446
1447
1448
1449
1450
1451
1452
1453
1454
1455
1456
1457
1458
1459
1460
1461
1462
1463
1464
1465
1466
1467
1468
200 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 1469
1470
1471
1472
1473
1474
1475
1476
1477
1478
1479
1480
1481
1482
1483
1484
1485
1486
1487
1488
1489
1490
1491
1492
1493
1494
1495
1496
1497
201 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 1498
1499
1500
1501
1502
1503
1504
1505
1506
1507
1508
1509
1510
1511
1512
1513
1514
1515
1516
1517
1518
1519
1520
1521
1522
1523
1524
1525
1526
202 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 1527
1528
1529
1530
1531
1532
1533
1534
1535
1536
1537
1538
1539
1540
1541
1542
1543
1544
1545
1546
1547
1548
1549
1550
1551
1552
1553
1554
1555
203 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 1556
1557
1558
1559
1560
1561
1562
1563
1564
1565
1566
1567
1568
1569
1570
1571
1572
1573
1574
1575
1576
1577
1578
1579
1580
1581
1582
1583
1584
204 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 1585
1586
1587
1588
1589
1590
1591
1592
1593
1594
1595
1596
1597
1598
1599
1600
1601
1602
1603
1604
1605
1606
1607
1608
1609
1610
1611
1612
205 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 1613
1614
1615
1616
1617
1618
1619
1620
1621
1622
1623
1624
1625
1626
1627
1628
1629
1630
1631
206 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 1632
1633
1634
1635
1636
1637
1638
1639
1640
1641
1642
1643
1644
1645
1646
1647
1648
1649
1650
1651
1652
1653
1654
1655
1656
1657
1658
1659
1660
1661
1662
1663
1664
1665
1666
1667
1668
1669
1670
208 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 1671
1672
1673
1674
1675
1676
1677
1678
1679
1680
1681
1682
1683
1684
1685
1686
1687
1688
1689
209 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 1690
1691
1692
1693
1694
1695
1696
1697
1698
1699
1700
1701
1702
1703
1704
1705
1706
1707
1708
1709
1710
210 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 1711
1712
1713
1714
1715
1716
1717
1718
1719
1720
1721
1722
1723
1724
1725
1726
1727
1728
1729
1730
1731
211 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 1732
1733
1734
1735
1736
1737
1738
1739
1740
1741
1742
1743
1744
1745
1746
1747
1748
1749
1750
1751
212 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 1752
1753
1754
1755
1756
1757
1758
1759
1760
1761
1762
1763
1764
1765
1766
1767
1768
1769
1770
1771
1772
213 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 1773
1774
1775
1776
1777
1778
1779
1780
1781
1782
1783
1784
1785
1786
1787
1788
1789
1790
1791
1792
1793
1794
1795
1796
1797
1798
1799
1800
1801
1802
1803
1804
1805
1806
1807
1808
1809
1810
1811
1812
1813
1814
1815
1816
1817
1818
1819
1820
1821
1822
1823
1824
1825
1826
1827
1828
1829
1830
1831
1832
216 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 1833
1834
1835
1836
1837
1838
1839
1840
1841
1842
1843
1844
1845
1846
1847
1848
1849
1850
1851
1852
217 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 1853
1854
1855
1856
1857
1858
1859
1860
1861
1862
1863
1864
1865
1866
1867
1868
1869
1870
1871
1872
1873
218 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 1874
1875
1876
1877
1878
1879
1880
1881
1882
1883
1884
1885
1886
1887
1888
1889
1890
1891
1892
1893
1894
219 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 1895
1896
1897
1898
1899
1900
1901
1902
1903
1904
1905
1906
1907
1908
1909
1910
1911
1912
1913
1914
1915
1916
1917
1918
1919
220 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 1920
1921
1922
1923
1924
1925
1926
1927
1928
1929
1930
1931
1932
1933
1934
1935
1936
1937
1938
1939
1940
1941
1942
1943
1944
1945
1946
221 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 1947
1948
1949
1950
1951
1952
1953
1954
1955
1956
1957
1958
1959
1960
1961
1962
1963
1964
1965
1966
1967
1968
1969
1970
1971
1972
1973
222 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 1974
1975
1976
1977
1978
1979
1980
1981
1982
1983
1984
1985
1986
1987
1988
1989
1990
1991
1992
1993
1994
1995
1996
1997
1998
1999
2000
223 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
2027
224 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 2028
2029
2030
2031
2032
2033
2034
2035
2036
2037
2038
2039
2040
2041
2042
2043
2044
2045
2046
2047
2048
2049
2050
2051
2052
2053
2054
225 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 2055
2056
2057
2058
2059
2060
2061
2062
2063
2064
2065
2066
2067
2068
2069
2070
2071
2072
2073
2074
2075
2076
2077
2078
2079
2080
2081
226 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 2082
2083
2084
2085
2086
2087
2088
2089
2090
2091
2092
2093
2094
2095
2096
2097
2098
2099
2100
2101
2102
2103
2104
2105
2106
2107
2108
227 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 2109
2110
2111
2112
2113
2114
2115
2116
2117
2118
2119
2120
2121
2122
2123
2124
2125
2126
2127
2128
2129
2130
2131
2132
2133
2134
2135
2136
228 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 2137
2138
2139
2140
2141
2142
2143
2144
2145
2146
2147
2148
2149
2150
2151
2152
2153
2154
2155
2156
2157
2158
2159
2160
2161
2162
2163
229 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 2164
2165
2166
2167
2168
2169
2170
2171
2172
2173
2174
2175
2176
2177
2178
2179
2180
2181
2182
2183
2184
2185
2186
2187
2188
2189
2190
230 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 2191
2192
2193
2194
2195
2196
2197
2198
2199
2200
2201
2202
2203
2204
2205
2206
2207
2208
2209
2210
2211
2212
2213
2214
2215
2216
2217
231 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 2218
2219
2220
2221
2222
2223
2224
2225
2226
2227
2228
2229
2230
2231
2232
2233
2234
2235
2236
2237
2238
2239
2240
2241
2242
2243
2244
232 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 2245
2246
2247
2248
2249
2250
2251
2252
2253
2254
2255
2256
2257
2258
2259
2260
2261
2262
2263
2264
2265
2266
2267
2268
2269
2270
2271
233 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 2272
2273
2274
2275
2276
2277
2278
2279
2280
2281
2282
2283
2284
2285
2286
2287
2288
2289
2290
2291
2292
2293
2294
2295
2296
2297
2298
234 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 2299
2300
2301
2302
2303
2304
2305
2306
2307
2308
2309
2310
2311
2312
2313
2314
2315
2316
2317
2318
2319
2320
2321
2322
2323
2324
2325
235 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 2326
2327
2328
2329
2330
2331
2332
2333
2334
2335
2336
2337
2338
2339
2340
2341
2342
2343
2344
2345
2346
2347
2348
2349
2350
2351
2352
236 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 2353
2354
2355
2356
2357
2358
2359
2360
2361
2362
2363
2364
2365
2366
2367
2368
2369
2370
2371
2372
2373
2374
2375
2376
2377
2378
2379
237 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 2380
2381
2382
2383
2384
2385
2386
2387
2388
2389
2390
2391
2392
2393
2394
2395
2396
2397
2398
2399
2400
2401
2402
2403
2404
2405
2406
238 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 2407
2408
2409
2410
2411
2412
2413
2414
2415
2416
2417
2418
2419
2420
2421
2422
2423
2424
2425
2426
2427
2428
2429
2430
2431
2432
2433
239 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 2434
2435
2436
2437
2438
2439
2440
2441
2442
2443
2444
2445
2446
2447
2448
2449
2450
2451
2452
2453
2454
2455
2456
2457
2458
2459
2460
240 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 2461
2462
2463
2464
2465
2466
2467
2468
2469
2470
2471
2472
2473
2474
2475
2476
2477
2478
2479
2480
2481
2482
2483
2484
2485
2486
2487
241 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 2488
2489
2490
2491
2492
2493
2494
2495
2496
2497
2498
2499
2500
2501
2502
2503
2504
2505
2506
2507
2508
2509
2510
2511
2512
2513
2514
242 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 2515
2516
2517
2518
2519
2520
2521
2522
2523
2524
2525
2526
2527
2528
2529
2530
2531
2532
2533
2534
2535
2536
2537
2538
2539
243 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 2540 Appendix B: Full Xml Schema
Prefi Sectio Schema name x n http://contracts.microsoft.com/WindowsServerEssentials/2011/09/WebApi tns1 7.1 http://schemas.datacontract.org/2004/07/Microsoft.WindowsServerSolutions.Storage tns2 7.2 http://schemas.microsoft.com/2003/10/Serialization/Arrays tns4 7.3 http://schemas.microsoft.com/2003/10/Serialization/ tns5 7.6 http://schemas.datacontract.org/2004/07/Microsoft.WindowsServerSolutions.AzureADObjectM tns6 7.4 odel http://schemas.datacontract.org/2004/07/System.Collections.ObjectModel tns7 7.5 http://schemas.datacontract.org/2004/07/Microsoft.WindowsServerSolutions.WebApi.Manage tns8 7.7 ment.Storage http://schemas.datacontract.org/2004/07/Microsoft.WindowsServerSolutions.O365Integration tns9 7.8 http://schemas.microsoft.com/Message tns10 7.9
2540.1 http://contracts.microsoft.com/WindowsServerEssentials/2011/09/WebA pi Schema
2541
2542
2543
2544
2545
2546
2547
2548
2549
2550
2551
2552
244 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 2553
2554
2555
2556
2557
2558
2559
2560
2561
2562
2563
2564
2565
2566
2567
2568
2569
2570
2571
2572
2573
2574
2575
2576
2577
2578
2579
245 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 2580
2581
2582
2583
2584
2585
2586
2587
2588
2589
2590
2591
2592
2593
2594
2595
2596
2597
2598
2599
2600
2601
2602
2603
2604
2605
2606
246 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 2607
2608
2609
2610
2611
2612
2613
2614
2615
2616
2617
2618
2619
2620
2621
2622
2623
2624
2625
2626
2627
2628
2629
2630
2631
2632
2633
247 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 2634
2635
2636
2637
2638
2639
2640
2641
2642
2643
2644
2645
2646
2647
2648
2649
2650
2651
2652
2653
2654
2655
2656
2657
2658
2659
2660
248 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 2661
2662
2663
2664
2665
2666
2667
2668
2669
2670
2671
2672
2673
2674
2675
2676
2677
2678
2679
2680
2681
2682
2683
2684
2685
2686
2687
249 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 2688
2689
2690
2691
2692
2693
2694
2695
2696
2697
2698
2699
2700
2701
2702
2703
2704
2705
2706
2707
2708
2709
2710
2711
2712
2713
2714
250 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 2715
2716
2717
2718
2719
2720
2721
2722
2723
2724
2725
2726
2727
2728
2729
2730
2731
2732
2733
2734
2735
2736
2737
2738
2739
251 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 2740
2741
2742
2743
2744
2745
2746
2747
2748
2749
2750
2751
2752
2753
2754
2755
2756
2757
2758
2759
2760
2761
2762
2763
2764
2765
2766
252 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 2767
2768
2769
2770
2771
2772
2773
2774
2775
2776
2777
2778
2779
2780
2781
2782
2783
2784
2785
2786
2787
2788
2789
2790
2791
2792
2793
253 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 2794
2795
2796
2797
2798
2799
2800
2801
2802
2803
2804
2805
2806
2807
2808
2809
2810
2811
2812
2813
2814
2815
2816
2817
2818
2819
2820
2821
2822
254 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 2823
2824
2825
2826
2827
2828
2829
2830
2831
2832
2833
2834
2835
2836
2837
2838
2839
2840
2841
2842
2843
2844
2845
2846
2847
2848
2849
2850
255 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 2851
2852
2853
2854
2855
2856
2857
2858
2859
2860
2861
2862
2863
2864
2865
2866
2867
2868
2869
2870
2871
2872
2873
2874
2875
2876
256 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 2877
2878
2879
2880
2881
2882
2883
2884
2885
2886
2887
2888
2889
2890
2891
2892
2893
2894
2895
2896
2897
2898
2899
2900
2901
2902
257 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 2903
2904
2905
2906
2907
2908
2909
2910
2911
2912
2913
2914
2915
2916
2917
2918
2919
2920
2921
2922
2923
2924
2925
2926
2927
2928
2929
2930
2931
258 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 2932
2933
2934
2935
2936
2937
2938
2939
2940
2941
2942
2943
2944
2945
2946
2947
2948
2949
2950
2951
2952
2953
2954
2955
2956
2957
2958
2959
2960
259 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 2961
2962
2963
2964
2965
2966
2967
2968
2969
2970
2971
2972
2973
2974
2975
2976
2977
2978
2979
2980
2981
2982
2983
2984
2985
2986
260 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 2987
2988
2989
2990
2991
2992
2993
2994
2995
2996
2997
2998
2999
3000
3001
3002
3003
3004
3005
3006
3007
3008
3009
3010
3011
3012
261 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 3013
3014
3015
3016
3017
3018
3019
3020
3021
3022
3023
3024
3025
3026
3027
3028
3029
3030
3031
3032
3033
3034
3035
3036
3037
3038
262 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 3039
3040
3041
3042
3043
3044
3045
3046
3047
3048
3049
3050
3051
3052
3053
3054
3055
3056
3057
3058
3059
3060
3061
3062
3063
263 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 3064
3065
3066
3067
3068
3069
3070
3071
3072
3073
3074
3075
3076
3077
3078
3079
3080
3081
3082
3083
3084
3085
3086
3087
3088
264 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 3089
3090
3091
3092
3093
3094
3095
3096
3097
3098
3099
3100
3101
3102
3103
3104
3105
3106
3107
3108
3109
3110
3111
3112
3113
265 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 3114
3115
3116
3117
3118
3119
3120
3121
3122
3123
3124
3125
3126
3127
3128
3129
3130
3131
3132
3133
3134
3135
3136
3137
3138
266 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 3139
3140
3141
3142
3143
3144
3145
3146
3147
3148
3149
3150
3151
3152
3153
3154
3155
3156
3157
3158
3159
3160
3161
3162
3163
3164
267 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 3165
3166
3167
3168
3169
3170
3171
3172
3173
3174
3175
3176
3177
3178
3179
3180
3181
3182
3183
3184
3185
3186
3187
3188
3189
3190
3191
268 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 3192
3193
3194
3195
3196
3197
3198
3199
3200
3201
3202
3203
3204
3205
3206
3207
3208
3209
3210
3211
3212
3213
3214
3215
3216
3217
3218
3219
269 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 3220
3221
3222
3223
3224
3225
3226
3227
3228
3229
3230
3231
3232
3233
3234
3235
3236
3237
3238
3239
3240
3241
3242
3243
3244
3245
3246
3247
270 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 3248
3249
3250
3251
3252
3253
3254
3255
3256
3257
3258
3259
3260
3261
3262
3263
3264
3265
3266
3267
3268
3269
3270
3271
3272
271 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 3273
3274
3275
3276
3277
3278
3279
3280
3281
3282
3283
3284
3285
3286
3287
3288
3289
3290
3291
3292
3293
3294
3295
3296
3297
3298
272 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 3299
3300
3301
3302
3303
3304
3305
3306
3307
3308
3309
3310
3311
3312
3313
3314
3315
3316
3317
3318
3319
3320
3321
3322
3323
3324
273 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 3325
3326
3327
3328
3329
3330
3331
3332
3333
3334
3335
3336
3337
3338
3339
3340
3341
3342
3343
3344
3345
3346
3347
3348
3349
3350
274 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 3351
3352
3353
3354
3355
3356
3357
3358
3359
3360
3361
3362
3363
3364
3365
3366
3367
3368
3369
3370
3371
3372
3373
3374
3375
3376
3377
275 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 3378
3379
3380
3381
3382
3383
3384
3385
3386
3387
3388
3389
3390
3391
3392
3393
3394
3395
3396
3397
3398
3399
3400
3401
276 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 3402
3403
3404
3405
3406
3407
3408
3409
3410
3411
3412
3413
3414
3415
3416
3417
3418
3419
3420
3421
3422
3423
3424
3425
3426
3427
3428
3429
3430
277 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 3431
3432
3433
3434
3435
3436
3437
3438
3439
3440
3441
3442
3443
3444
3445
3446
3447
3448
3449
3450
3451
3452
3453
3454
3455
3456
3457
3458
3459
278 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 3460
3461
3462
3463
3464
3465
3466
3467
3468
3469
3470
3471
3472
3473
3474
3475
3476
3477
3478
3479
3480
3481
3482
3483
279 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 3484
3485
3486
3487
3488
3489
3490
3491
3492
3493
3494
3495
3496
3497
3498
3499
3500
3501
3502
3503
3504
3505
3506
3507
3508
3509
280 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 3510
3511
3512
3513
3514
3515
3516
3517
3518
3519
3520
3521
3522
3523
3524
3525
3526
3527
3528
3529
3530
3531
3532
3533
281 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 3534
3535
3536
3537
3538
3539
3540
3541
3542
3543
3544
3545
3546
3547
3548
3549
3550
3551
3552
3553
3554
3555
3556
3557
3558
3559
3560
282 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 3561
3562
3563
3564
3565
3566
3567
3568
3569
3570
3571
3572
3573
3574
3575
3576
3577
3578
3579
3580
3581
3582
3583
3584
3585
3586
3587
283 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 3588
3589
3590
3591
3592
3593
3594
3595
3596
3597
3598
3599
3600
3601
3602
3603
3604
3605
3606
3607
3608
3609
3610
3611
3612
3613
284 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 3614
3615
3616
3617
3618
3619
3620
3621
3622
3623
3624
3625
3626
3627
3628
3629
3630
3631
3632
3633
3634
3635
3636
3637
3638
3639
3640
3641
3642
285 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 3643
3644
3645
3646
3647
3648
3649
3650
3651
3651.1 http://schemas.datacontract.org/2004/07/Microsoft.WindowsServerSolut ions.Storage Schema
3652
3653
3654
3655
3656
3657
3658
3659
3660
3661
3662
3663
3664
3664.1 http://schemas.microsoft.com/2003/10/Serialization/Arrays Schema
3665
286 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 3666
3667
3668
3669
3670
3671
3672
3673
3673.1 http://schemas.datacontract.org/2004/07/Microsoft.WindowsServerSolut ions.AzureADObjectModel Schema
3674
3675
3676
3677
3678
3679
3680
3681
3682
3683
3684
3685
3686
287 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 3687
3688
3689
3690
3691
3692
3693
3694
3695
3696
3697
3698
3699
3700
3701
3702
3703
3704
3705
3706
3707
3708
3709
3710
3711
3712
3713
288 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 3714
3715
3716
3717
3718
3719
3720
3721
3722
3723
3724
3725
3726
3727
3728
3729
3730
3731
3732
3733
3734
3735
3736
3737
3738
3739
3740
3741
289 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 3742
3743
3744
3745
3746
3747
3748
3749
3750
3751
3752
3753
3754
3755
3756
3757
3758
3759
3760
3761
3762
3763
3764
3765
3766
3767
3768
3769
290 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 3770
3771
3772
3773
3774
3775
3776
3777
3778
3779
3780
3781
3782
3783
3784
3785
3786
3787
3788
3789
3790
3791
3792
3793
3794
3795
3796
3797
3798
291 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 3799
3800
3801
3802
3803
3804
3805
3806
3807
3808
3809
3810
3811
3812
3813
3814
3815
3816
3817
3818
3819
3820
3821
3822
3823
3824
292 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 3825
3826
3827
3828
3829
3830
3831
3832
3833
3834
3835
3836
3837
3838
3839
3840
3841
3842
3843
3844
3845
3846
3847
3848
3849
3850
3851
293 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 3852
3852.1 http://schemas.datacontract.org/2004/07/System.Collections.ObjectMod el Schema
3853
3854
3855
3856
3857
3858
3859
3860
3861
3862
3863
3864
3865
3866
3867
3868
3869
3870
3871
3872
294 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 3873
3874
3875
3876
3877
3878
3879
3880
3881
3882
3883
3884
3885
3886
3887
3888
3889
3890
3891
3892
3893
3894
3895
3896
295 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 3897
3898
3899
3900
3901
3902
3903
3904
3905
3906
3907
3908
3909
3910
3911
3912
3913
3914
3915
3916
3917
3918
3919
3920
296 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 3921
3922
3922.1 http://schemas.microsoft.com/2003/10/Serialization/ Schema
3923
3924
3925
3926
3927
3928
3929
3930
3931
3932
3933
3934
3935
3936
3937
3938
3939
3940
3941
3942
3943
3944
3945
3946
297 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 3947
3948
3949
3950
3951
3952
3953
3954
3955
3956
3957
3958
3959
3960
3961
3962
3963
3964
3964.1 http://schemas.datacontract.org/2004/07/Microsoft.WindowsServerSolut ions.WebApi.Management.Storage Schema
3965
3966
3967
3968
3969
3970
3971
298 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 3972
3973
3974
3975
3976
3977
3978
3979
3980
3981
3982
3983
3984
3985
3986
3987
3988
3989
3990
3991
3992
3993
3994
3995
3996
3997
3998
3999
299 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 4000
4001
4002
4003
4004
4005
4006
4007
4008
4009
4010
4011
4012
4013
4014
4015
4016
4017
4018
4019
4020
4021
4021.1 http://schemas.datacontract.org/2004/07/Microsoft.WindowsServerSolut ions.O365Integration Schema
4022
4023
4024
300 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 4025
4026
4027
4028
4029
4030
4031
4031.1 http://schemas.microsoft.com/Message Schema
4032
4033
4034
4035
4036
4037
301 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 4038 Appendix C: Product Behavior The information in this specification is applicable to the following Microsoft products or supplemental software. References to product versions include released service packs. § Windows Server 2012 R2 operating system § Windows Server 2016 operating system Exceptions, if any, are noted below. If a service pack or Quick Fix Engineering (QFE) number appears with the product version, behavior changed in that service pack or QFE. The new behavior also applies to subsequent service packs of the product unless otherwise specified. If a product edition appears with the product version, behavior is different in that product edition. Unless otherwise specified, any statement of optional behavior in this specification that is prescribed using the terms "SHOULD" or "SHOULD NOT" implies product behavior in accordance with the SHOULD or SHOULD NOT prescription. Unless otherwise specified, the term "MAY" implies that the product does not follow the prescription. <1> Section 2.2.4.11: This complex type is not available in the Windows Server 2012 operating system. <2> Section 2.2.4.12: This complex type is not available in Windows Server 2012. <3> Section 2.2.4.40: This complex type is not available in Windows Server 2012. <4> Section 2.2.4.41: This complex type is not available in Windows Server 2012. <5> Section 2.2.4.42: This complex type is not available in Windows Server 2012. <6> Section 2.2.4.43: This complex type is not available in Windows Server 2012. <7> Section 2.2.4.44: This complex type is not available in Windows Server 2012. <8> Section 2.2.4.45: This complex type is not available in Windows Server 2012. <9> Section 2.2.4.46: This complex type is not available in Windows Server 2012. <10> Section 2.2.5.1: This simple type is not available in Windows Server 2012. <11> Section 3.7.5.1.1: In Windows, this API only supports administrator calls and standard user calling. It returns a list of devices that are managed by the server. If the caller is a standard user, this API returns a list of devices for which the standard user has remote access permission. <12> Section 3.11.3: When using the Media Web APIs on Windows Server 2012 R2, an HTTP 500 error occurs unless the Windows Server Essentials Media Pack is installed.
302 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 <13> Section 3.13.5.10: The usergroups parameter is supported only in Windows Server 2012 R2.
303 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 4039 Change Tracking This section identifies changes that were made to this document since the last release. Changes are classified as Major, Minor, or None. The revision class Major means that the technical content in the document was significantly revised. Major changes affect protocol interoperability or implementation. Examples of major changes are: § A document revision that incorporates changes to interoperability requirements. § A document revision that captures changes to protocol functionality. The revision class Minor means that the meaning of the technical content was clarified. Minor changes do not affect protocol interoperability or implementation. Examples of minor changes are updates to clarify ambiguity at the sentence, paragraph, or table level. The revision class None means that no new technical changes were introduced. Minor editorial and formatting changes may have been made, but the relevant technical content is identical to the last released version. The changes made to this document are listed in the following table. For more information, please contact [email protected]. Revisi Section Description on class
7160 : Revised to indicate that this 2.2.3.30 overwrite Minor flag has a Boolean value.
7160 : Revised to indicate that this 2.2.3.31 overwritepermissions Minor flag has a Boolean value.
7157 : Changed type from DateTime to xs:dateTime where it appears in 2.2.4 Complex Types Minor complex type definitions throughout this section.
7156 : Changed the minoccurs value from 1 to 0 in each of the complex type definitions in 2.2.4 Complex Types Minor sections 2.2.4.2 (ArrayOfAlertInfo) through 2.2.4.23 (ArrayOfWebApiPro vider).
7159 : Added a product behavior note to indicate 2.2.4.11 ArrayOfMetadataBase Major product applicability for this complex type.
304 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 Revisi Section Description on class
7159 : Added a product behavior note to indicate 2.2.4.12 ArrayOfMetadataItemStream Major product applicability for this complex type.
7155 : Added a new 2.2.4.37 Office365Mailbox section for this Major complex type.
7155 : Added a new 2.2.4.38 ExchangeServerMailbox section for this Major complex type.
7155 : Added a new 2.2.4.39 HostedMailbox section for this Major complex type.
7159 : Added a product behavior note to indicate 2.2.4.40 MetadataBase Major product applicability for this complex type.
7159 : Added a product behavior note to indicate 2.2.4.41 MetadataContainer Major product applicability for this complex type.
7159 : Added a product behavior note to indicate 2.2.4.42 MetadataDetailResult Major product applicability for this complex type.
7159 : Added a product behavior note to indicate 2.2.4.43 MetadataItem Major product applicability for this complex type.
7159 : Added a product behavior note to indicate 2.2.4.44 MetadataItemStream Major product applicability for this complex type.
7159 : Added a product behavior note to indicate 2.2.4.45 MetadataResult Major product applicability for this complex type.
7159 : Added a product behavior note to indicate 2.2.4.46 MetadataStreamResult Major product applicability for this complex type.
305 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 Revisi Section Description on class
7159 : Added a product behavior note to indicate 2.2.5.1 ContainerType Major product applicability for this simiple type.
7155 : Added a new 2.2.5.8 StreamBody section for this Major simple type.
7155 : Added a new 2.2.5.9 char section for this Major simple type.
7155 : Added a new 2.2.5.10 duration section for this Major simple type.
7162 : Updated the 3.3.5.1.1 GET URI to include the Minor request definition.
7162 : Updated the 3.3.5.2.1 GET URI to include the Minor request definition.
7162 : Updated the 3.3.5.3.1 GET URI to include the Minor request definition.
7161 : Added a 3.15.5.1.1.3 Processing Details description for the Minor deviceid parameter.
7161 : Added a 3.15.5.2 /notification/unsubscribe?deviceid={deviceid} description for the Minor deviceid parameter.
Changed "q6, q7" 7 Appendix B: Full Xml Schema to "tns10" in the Minor Prefix column .
Added definitions 7.4 for FirstName and http://schemas.datacontract.org/2004/07/Microsoft.WindowsServerSolution LastName elements Minor s.AzureADObjectModel Schema for the MSOUser complex type. Index A Logout example 199 Retrieve the Metadata for Items within a Folder Applicability 19 example 197 Upload a File example 199 C F Capability negotiation 19 Change tracking 258 Fields - vendor-extensible 19 Common data types 20
E G Glossary 17 Examples Create a Folder example 198 Get Server Folders example 196 I Get Server Information example 195 Login example 195 Ialertmanagement server
306 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 Abstract data model 128 Abstract data model 143 Higher-layer triggered events 129 Higher-layer triggered events 143 Initialization 129 Initialization 143 Message processing events and sequencing rules 129 Message processing events and sequencing rules 143 Other local events 135 Other local events 145 Timer events 135 Timer events 144 Timers 129 Timers 143 Iazureadmanagement server Iservicemanagement server Abstract data model 98 Abstract data model 140 Higher-layer triggered events 99 Higher-layer triggered events 141 Initialization 99 Initialization 141 Message processing events and sequencing rules 99 Message processing events and sequencing rules 141 Other local events 114 Other local events 142 Timer events 113 Timer events 142 Timers 98 Timers 141 Icustomizationmanagement server Isharepointsitemgmt server Abstract data model 145 Abstract data model 190 Higher-layer triggered events 145 Higher-layer triggered events 190 Initialization 145 Initialization 190 Message processing events and sequencing rules 145 Message processing events and sequencing rules 190 Other local events 146 Other local events 191 Timer events 146 Timer events 191 Timers 145 Timers 190 Idevicemanagement server Istoragemanagement server Abstract data model 135 Abstract data model 159 Higher-layer triggered events 136 Higher-layer triggered events 160 Initialization 136 Initialization 160 Message processing events and sequencing rules 136 Message processing events and sequencing rules 160 Other local events 140 Other local events 173 Timer events 140 Timer events 173 Timers 136 Timers 160 Ifilecontentaccessservice server Iusermanagement server Abstract data model 78 Abstract data model 174 Higher-layer triggered events 78 Higher-layer triggered events 174 Initialization 78 Initialization 174 Message processing events and sequencing rules 79 Message processing events and sequencing rules 174 Other local events 83 Other local events 189 Timer events 83 Timer events 189 Timers 78 Timers 174 Ifileoperationservice server Iwindowsphonemanagement server Abstract data model 83 Abstract data model 191 Higher-layer triggered events 83 Higher-layer triggered events 191 Initialization 83 Initialization 191 Message processing events and sequencing rules 83 Message processing events and sequencing rules 192 Other local events 98 Other local events 194 Timer events 98 Timer events 194 Timers 83 Timers 191 Imailboxmanagement server Abstract data model 114 M Higher-layer triggered events 114 Initialization 114 Messages Message processing events and sequencing rules 114 transport 20 Other local events 128 Timer events 128 Timers 114 N Imediamanagement server Abstract data model 147 Namespaces 20 Higher-layer triggered events 147 Normative references 18 Initialization 147 Message processing events and sequencing rules 147 O Other local events 159 Timer events 159 Overview (synopsis) 18 Timers 147 Implementer - security considerations 201 Index of security parameters 201 P Informative references 18 Introduction 17 Parameters - security index 201 Iservermanagement server Preconditions 19
307 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017 Prerequisites 19 Sessionservice server Product behavior 257 Abstract data model 75 Protocol examples Higher-layer triggered events 75 Create a Folder 198 Initialization 75 Get Server Folders 196 Message processing events and sequencing rules 75 Get Server Information 195 Other local events 78 Login 195 Timer events 78 Logout 199 Timers 75 Retrieve the Metadata for Items within a Folder 197 Standards assignments 19 Upload a File 199 T R Tracking changes 258 References Transport 20 informative 18 common data types 20 normative 18 namespaces 20 Relationship to other protocols 19 V S Vendor-extensible fields 19 Security Versioning 19 implementer considerations 201 parameter index 201
308 / 308 [MS-SFMWA] - v20170316 Server and File Management Web APIs Protocol Copyright © 2017 Microsoft Corporation Release: March 16, 2017