Advanced integration

Collabora Online uses a WOPI-like protocol to interact with hosts who want to integrate Collabora Online in them.

Refer to WOPI docs for further details on the protocol’s inspiration.

CheckFileInfo response properties


A string containing the base name of the file, omitting its path.


Disables print functionality in libreoffice online backend. If true, HidePrintOption is assumed to be true.


A programmatic string identifier for the owner of the file.


A string for the domain the host page sends/receives PostMessages from, we only listen to messages from this domain.


Size of the file in bytes (64bit)


The ID of file (like the wopi/files/ID) can be a non-existing file. In that case, the file will be created from a template when the template (eg. an OTT file) is specified as TemplateSource in the CheckFileInfo response.

The TemplateSource is supposed to be an URL like https://somewhere/accessible/ that is accessible by the Online.

For the actual saving of the content, normal PutFile mechanism will be used.


A boolean flag, indicating whether the user has permission to edit and/or over-write the file. If not set PutFile will fail.


A boolean flag indicating that the user cannot Save-As on this server, so PutRelativeFile will fail.


A programmatic string identifier of the user.


A string representing the name of the user for display in the UI.

While nominally an optional field, it is used to identify the author of changes in documents. When missing, UnknownUser will be used instead, with a possible suffix with the UserId.

Strongly recommended to set it to a valid value.

CheckFileInfo extended response properties


If set to true, hides the print option from the file menu bar in the UI


If set to true, hides the save button from the toolbar and file menubar in the UI


Hides Download as option in the file menubar


Disables export functionality in backend. If set to true, HideExportOption is assumed to be true


Disables copying from the document in libreoffice online backend. Pasting into the document would still be possible. However, it is still possible to do an “internal” cut/copy/paste.


Disables displaying of the explanation text on the overlay when the document becomes inactive or killed. With this, the JS integration must provide the user with appropriate message when it gets Session_Closed or User_Idle postMessage’s.


Indicate that the integration wants to handle the downloading of pdf for printing or svg for slideshows or exported document, because it cannot rely on browser’s support for downloading.

When this is set to true, the user’s eg. Print action will trigger a postMessage called Download_As, with the following JSON in the Values:

{ Type: 'print'|'slideshow'|'export', URL: ...url you use for the actual downloading... }


If set to true, it allows the document owner (the one with OwnerId =UserId) to send a closedocument message (see protocol.txt)


JSON object that contains additional info about the user, namely the avatar image.

Example: User’s additional info
'UserExtraInfo' => [ 'avatar' => 'http://url/to/user/avatar', 'mail' => '' ]

Note: There is strict Content Security Policy that restricts image resources (img-src), therefore the avatar URL must not violate the CSP, otherwise it will show as broken images.


If set to a non-empty string, is used for rendering a watermark-like text on each tile of the document

Note: It is possible to just hide print, save, export options while still being able to access them from other hosts using PostMessage API

PostMessage extensions


Was extended with field ‘Status’ with Document_Loaded value when document was loaded successfully and ‘Failed’ in other case.

PutFile headers

PutFile additionally indicates whether the user has modified the document before the save, or if they just pressed the Save button without any modification. The following header:


will have the value true or false accordingly.

To distinguish auto-save vs. explicit user requests to save, the following header:


will have the value true when the PutFile is triggered by auto-save, and false when triggered by explicit user operation (Save button or menu entry).

When the document gets cleaned up from memory (e.g. when all users disconnect), an automatic save will be triggered. In this case the following header will be set to true:


Detecting external document change

Locking is omitted from our WOPI-like protocol since it goes against common EFSS solutions usage. Instead, Collabora Online uses timestamps to detect document changes.

When the document is updated in your storage while being edited in Collabora Online and there are unsaved changes, we detect it as soon as possible and ask the user if he/she would like to overwrite the changes or reload the new document from the storage.

In case there are no unsaved changes, we reload the new document without asking the user.

To support this feature, the host implementation has to specify LastModifiedTime field in both CheckFileInfo and PutFile calls.

Additionally, hosts must check for a header in PutFile response:


This header contains the ISO8601 round-trip formatted time of file’s last modified time in storage, as known by Collabora Online. In case this header is present and its value does not match the file’s modified time in storage, it indicates that document being edited is not the one that is present in the storage.

Hosts should not save the file to storage in such cases and respond with HTTP 409 along with Collabora Online specific status code:

HTTP 409 with JSON
     'COOLStatusCode': 1010

When the user chooses “overwrite” when asked how to resolve the conflict, Collabora Online will attempt one more save operation, but this time it will lack the X-COOL-WOPI-Timestamp header, which means “save regardless of state of the file”.

Checking for available features

With new features, it is important for the integrations to know if the Online they are using is supporting them. For this reason, we have introduced a /hosting/capabilities endpoint that returns a JSON with information about the availability of various features.

Currently the following are present:

  • convert-to: {available: true/false }

    The property available is true when the convert-to functionality is present and correctly accessible from the WOPI host.

  • hasTemplateSource: true/false

    is true when the Online supports the TemplateSource CheckFileInfo property.

  • hasMobileSupport: true/false

    is true when the Online has a good support for the mobile devices and responsive design.

Modifying discovery.xml

The discovery.xml defines which part of Collabora Online can be used for a certain file type and what action should be used.

The following is a snipped from discovery.xml

<app name="writer" favIconUrl="images/x-office-document.svg">
   <action name="view" default="true" ext="sxw"/>
   <action name="edit" default="true" ext="odt"/>
<app name="draw">
   <action name="view_comment" ext="pdf"/>

The supported actions are “edit”, “view” and a special “view_comment”. When the action is “edit”, the document will open for editing. When the action is “view”, the document will open in read-only mode for viewing. When the action is set to “view_comment”, the document will open read-only, but adding or editing comments will still be possible.

The “view_comment” mode is useful for PDF documents, where adding and editing comments is allowed, but otherwise no other editing should be allowed to be performed.