Get All Project Teams
Request
GET <REST API URL>
/projectteams?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 ProjectTeams: access(project: project, with: role) — Teams that have the given role in the given project access(project: project, with: permission) — Teams that have the given permission in the given project access(project: project) — Teams that have some role in the given project access(with: role) — Teams that have the given role in some projects access(with: permission) — Teams that have the given permission in some projects group: group — Teams containing the given group has: ownRole — Teams with own roles has: groups — Teams with included groups id: value — Project team with the given ID name: projectName — Team of project with the given name ownRole: role — Teams that own the given role project: project — Team of the given project |
orderBy | Order results. See Sorting Syntax for details. Roles can be ordered by the following fields: name |
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. |