![]() |
API Documentation
|
The Covata API's interaction with specific Secure Objects and collections relies heavily on submitting requests to the API using the ID values of these items.
If your application does not store these items' IDs, information about a specific subset of items can be retrieved (as a list) by filtering all items recorded on the Covata Platform using navigable or memorable criteria, such as a 'search' substring that matches part of an item's name, or email address, first name or last name of the item's owner. From this manageable list of items retrieved from the Covata Platform, the required items' IDs can be obtained.
This page describes how to use Covata's API to retrieve a list of information about:
This page also describes how to sort, order and paginate any list of items retrieved using these procedures.
Notes:
- Before retrieving a list of Secure Objects and collections, your application must have a valid access token obtained by authenticating and authorizing a Covata user to the Covata Platform, where this user either:
For more information about authenticating and authorizing Covata users to the Covata Platform, see Initiating authentication and authorization on the Authentication and authorization page of this guide and the Configuring client applications page of the Safe Share Administrator's Guide.
- has the appropriate role to create their own items (i.e. the Originator role) or
- be a collaborator on items which other users have shared with them. For more information about the definition of a collaborator and sharing items, see Sharing items.
- The Supported roles (and conditions) sections of each API endpoint page (linked to from the procedures below) contain details about the roles and permissions that a Covata user requires for a successful request to the endpoint (along with a valid access token representing this user).
Information about immediate child items (i.e. both Secure Objects and collections) of a common parent can be retrieved as a list from the Covata Platform. This common parent can be either a parent collection of these child items, or the logical root level.
To retrieve this list of information about all immediate child items of a common parent, make a GET request to the <access-service>/api/v1/items API endpoint with the collectionId URL parameter whose value is either:
0 to specify items located at the logical root level.Information about all items whose name or owner's email address/first name/last name contains a specified string, irrespective of an item's location or ownership, can be retrieved as a list from the Covata Platform. (This is effectively a text search feature.)
To retrieve a list of information about all items whose name or owner's email address/first name/last name contains a specified string, make a GET request to the <access-service>/api/v1/items API endpoint with the searchText URL parameter whose value contains the specified string itself.
Note: It is not possible to specify both the searchText and collectionId (above) URL parameters in the same request.
Information about all items belonging to a Covata user (represented by an access token), or all items which this user has shared or is a collaborator on (i.e. the items' sharing status in relation to the user) can be retrieved as a list from the Covata Platform.
To retrieve this list of information about all items:
make a GET request to the <access-service>/api/v1/items API endpoint and specifying the view URL parameter with a value of:
owned-by-me to retrieve all items owned by the specified Covata user*,shared-with-me to retrieve all items that other Covata users have shared with the specified Covata user*,sharing to retrieve all items that the specified Covata user* has shared with other people, orall to retrieve all items that the specified Covata user* can access.* In each case, the specified Covata user is represented by its valid access token passed in the header of the request.
Tip: The view URL parameter can be used in conjunction with both the collectionId and searchText parameters (above) for additional filtering.
To retrieve information about all ancestral collections (back to the logical root level) of an item, make a GET request to the <access-service>/api/v1/items/{itemId}/ancestry API endpoint.
All ancestral collections from the logical root level through to the parent collection of item whose ID is specified in this request's URL is returned in the response. The response is a flat list of information about these ancestral collections in hierarchical order from the logical root level.
The list of information about all retrieved items from a common parent, filtered by text search or based on ownership or sharing status can be sorted, ordered and paginated by specifying the following additional URL parameters in the appropriate GET request to the <access-service>/api/v1/items API endpoint:
NAME - the item's name (which is the default value if this parameter is omitted),OWNER - the item's owner,MODIFIED - the date when the item was last modified, orCREATED - the date when the item was created.ASC - for ascending alphanumeric or chronological order (which is the default value if this parameter is omitted), orDESC - for descending alphanumeric or chronological order.10 by default.0 by default.For more information about the limit and offset URL parameters for paginating items returned in the response, refer to the descriptions of these parameters in the Optional parameters section on the <access-service>/api/v1/items page.