Get All Resources of a Project
Request
GET <REST API URL>
/projects/{project id
}/resources?fields=string
&$skip=int
&$top=int
&query=string
&orderBy=string
Parameter | Description |
---|---|
fields | Optional query parameter. Specifies a subset of the fields to be returned. Use Fields Syntax to define subset. |
$skip | Optional query parameter. Number of roles to skip before returning first entry of the page. |
$top | Optional query parameter. Max number of roles to return in the page. |
query | Filter query. See Query Syntax for the definition of supported logical operations syntax. Following fields and tuples are supported for Resources: has: type — Resources with some type has: homeUrl — Resources with some homeURL homeUrl: value — Resource with the given home URL id: value — Resource with the given ID key: resourceKey — Resources with the given key name: resourceName — Resources with the given name project: project — Resources in the given project service: service — Resources provided by the given service |
orderBy | Order results. See Sorting Syntax for details. Roles can be ordered by the following fields: key, name, project, service, type |
Response
Response Code | Meaning |
---|---|
200 OK | Successful request. |
400 Bad Request | Some of the parameters of the request are invalid (for example, required fields in the passed JSON object are missing). The response contains message describing the error. |
403 Forbidden | Requester has no access to the request. |
404 Not Found | Requested resource wasn't found. |
500 Internal Server Error | Failed to process request because of the server error. The response contains message describing the error. |
Last modified: 20 November 2017