Get root URLs and support flags. The endpoint that defines support and discovery for other endpoints. Meant to be used periodically for updating what the CLFS implementation supports and allowing gradual updates.

Discovery can return a static response and only use the storageId for URLs if 404 and 503 responses aren't meant to be used for controlling the status of a particular source.

CLFS only needs to implement one: FSURL or DiffURL, depending on technical capabilities and traffic estimates.

This endpoint may be called when the source is removed from Egnyte Protect. Source can use it to clean up access, credentials, cache or any other information no longer necessary.

List a folder with separate collections for its direct children - sub-folders and files.

Only one of folder listing and storage diff need to be implemented. If your software can produce diff listing it's the preferable option for performance and efficiency of tracking changes to the storage.

Folders and files lists are one level deep. Egnyte Protect will make requests for all non-empty nested folder listings to discover files there.

Endpoint may optionally support pagination of items in this folder using cursor.

Files can be represented in one of two ways:

• as a single file without a history, where Egnyte Protect assumes all other versions don't exist anymore,

• as a file with a complete list of all versions of the file that the system still holds; versions which disappear from the list are also removed in Egnyte Protect classification.

  Expand the 200 Folder listing -> files response to see all details

Alternative way of presenting storage contents especially useful when the storage structure is large and deeply nested.

Only one of folder listing and storage diff need to be implemented. If your software can produce diff listing it's the preferable option for performance and efficiency of tracking changes to the storage.

Files are represented with a single version id. All version remove actions can be represented as separate entries to maintain consistency in versions between systems.

An endpoint to return the file content.

If file content has requiresAuth set, this endpoint is necessary and the content.URL field is pointing to it.
If you can return public links to file content, but the links expire, the best option is to implement this endpoint and make it return a 302 redirecting to the public short-lived URL. That way you don't have to proxy the file content.

Report an issue with CLFS implementation. The endpoint will be called when errors are found in implementation - output doesn't validate etc.

Not all issues will be reported. An issue with a particular code occurring multiple times may be selectively de-duplicated to avoid flooding the endpoint.

Egnyte Protect will call this endpoint in order to register a webhook for storage events. Connector should register a webhook for a given storageId only once. Next call should override previous registration.

Endpoint for batch files remediation (delete or move).

Parameter operation describes if files should be deleted or moved to different location.

Parameter fileIds contains array of file IDs to be remediated.

Parameter sourceFolderId is ID of folder containing files being remediated.

Parameter leaveStubs is by default set to false. When set to true it indicates that for each file being remediated there should be a stub file created with original file name suffixed with .txt and content describing that this file was deleted/moved on specified date.

Parameter targetFolderId has meaning only for move operation. It indicates ID of folder into which files needs to be moved.

Parameter preserveStructure has meaning only for move operation. When set to true it indicates that files after move should have the same relative path to target folder as they had to source folder.