Get Project Team List
Get Project Team List
api/ProjectTeam
Query String
| Parameter | Required | Value |
|---|---|---|
| pinProjectId | Mandatory | PINProjectID |
| requestFor | Mandatory | |
| start | Optional | User Input |
Request Header
| Parameter | Required | Value |
|---|---|---|
| TokenKey | Mandatory | User Input |
| Page | Optional | User Input |
| PerPage | Optional | User Input |
Example of Response
TokenKey → Your-Key[
{
"ProjectTeamID": 12248,
"TeamName": "Owner Team",
"TeamMembersCount": 2
}
]Project Team Entity
| Property Name | Data Type |
|---|---|
| ProjectTeamID | Integer |
| TeamName | String |
| TeamMembersCount | Integer |
Enum : RequestFor
| Property Name | Description |
|---|---|
| 1 - AllInvitees | All Project Invitees |
| 2 - AcceptedInvitees | All Accepted Invitees |
| 3 - InviteesNotYetRejected | All Un–rejected Invitees |
Remarks:
-
For getting all records at a time do not add Page in request header.
-
Use PerPage parameter to change maximum number of records per page during population of paginated data; by default each page contains at most 10 records at a time.
-
Response header parameter Accept–Ranges will not come with paginated data and other response header parameters will not come for all records population.
-
If the paginated result is empty then response header parameter Max–Page will be 0 (zero) and there will be no other page related response header parameter.
-
Add start in query string only for filtering project team list by TeamName.