WOPI implementation requirements for mobile integration
The following describes the implementation requirements for Microsoft 365 for mobile integration.
Note
This content applies to Microsoft 365 for mobile. Both of the endpoints require the same level of WOPI implementation.
This section documents specific requirements for your WOPI implementation for integration with Microsoft 365 for mobile beyond what's documented in general for WOPI. Learn more about how Microsoft 365 for mobile uses these operations in the Operational flows for Microsoft 365 for mobile section.
Required WOPI Operations for Microsoft 365 for mobile
The following WOPI operations are required for integrating with Microsoft 365 for mobile. Operations not listed here aren't currently called by Microsoft 365 for mobile.
If some operations aren't supported for a specific user, file, or container, just be sure to return the correct values in CheckFileInfo and CheckContainerInfo.
File Operations
- CheckFileInfo
- GetFile
- Lock
- GetLock
- RefreshLock
- Unlock
- UnlockAndRelock
- PutFile
- EnumerateAncestors (files)
Container Operations
Ecosystem Operations
Bootstrapper
Future Support
While these WOPI operations aren't currently used by Microsoft 365 for mobile, they must be implemented. Microsoft 365 for mobile might use these operations in the future.
- RenameFile
- DeleteFile
- CreateChildContainer
- DeleteContainer
- RenameContainer
- GetEcosystem (files)
- GetEcosystem (containers)
Other Requirements
- The X-WOPI-ItemVersion header must be included on PutFile, Lock, and Unlock responses.
- For the Bootstrap operation, the Content-Type response header must be set to
application/json. - IsEduUser and LicenseCheckForEditIsEnabled are required on CheckFileInfo and CheckContainerInfo. The values from CheckFileInfo must match that of the file’s parent container.