Last updated: Dec 15, 2019 11:55
Gets the status of one or more items from the repository area specified by and optionally from the subarea within the repository specified. If the <repository> is not specified, the response returns items from all the subareas.
<repository> is specified as follows:
- media - the repository area for general media files
- datatables - the repository area for data table files
- scripts - the repository area for automation script files
<repositoryItemKey> is the location of the items within the repository, specified as a repository key that contains subarea and folder information.
Note: All REST API commands require authentication, see the general authentication methods here.
|securityToken*||string||A unique cryptographic key assigned to an authorized user.|
|admin||string||true to allow users with administrative credentials to get the status of one or more items from the repository of other automation users.|
|owner||string||The user name of the user who owns the item. This parameter is used in conjunction with the admin parameter to correctly identify items stored in PRIVATE or GROUP repositories of the owner. For example, if a user with administrative credentials wants to download an items list where the repositoryItemKey is PRIVATE:myItem.jpg or GROUP:myItem.jpg, specify the parameters asadmin=true and owner=itemUser.|
|group||string||The group name. This parameter is used in conjunction with the admin parameter to correctly identify items stored in GROUP repositories. For example, if a user with administrative credentials wants to download an items list for the repositoryItemKey, specify the parameters as admin=true and group= groupName.|
|responseFormat||string||json||Format of response: json, xml|
|detailed||true | false||false||Selects whether the info displayed for each Repository item includes creation and modification information, file type (simple or container), and the file key. Default is not to include this information.|
The response is a list of repository keys corresponding to the items located in the specified location within the repository.
Repository items are sorted as follows:
- Visibility: private, group, public, system.
- Within each visibility, files appear first, followed by folders.
- Folders and files are listed alphabetically.
Request without optional parameters
This example shows the request and response for listing the items in the appium folder located in the PUBLIC subarea of the media repository area.