The “path=” parameter is the most common parameter for storage API and is usually a mandatory one too. The section will lay down the common format adopted by all of them when specifying a path.

But note that the final path is subject to individual API semantic verification. Example, an API may reject a path because it is not pointing to an existing folder.

General form: [/][ <AreaName> [/relative_path_to_item | / ] ]

Examples:
path=/Private/subdir/My File.doc - specifying a particular file.

(Please note that the parameter should be appropriately urlencoded to path=%2FPrivate%2Fsubdir%2FMy%20File.doc but in the examples here we will not do it to avoid the clutter.)

path=/
This specifies the root, the point where all other storage area begin from.
path=/Company Share - specifying the Company Share area (folder)
path=Company Share - the leading / can be dropped

path=/Private/subdir/subdir/ - specifying a folder
path=/Private/subdir/subdir - trailing / not significant

The first part of the path is assumed to be an areaname (toplevel folder), e.g. “Public Share”, “Private”, etc. This could be optionally bracketed but should be considered as deprecated format. The leading “/” is optional, except when specifying “path=/”. The trailing “/” is optional in most API but can be significant in some (e.g. in CopyMove).