Appearance
Members API
A project's members are the users who reach it through one of its teams or through a direct project membership. List them to find the user IDs you can pass as assignee_id when creating or updating issues.
Permissions
| Action | Required Permission | Scope |
|---|---|---|
| List | Project access | In accessible projects |
Any user who can open the project can list its members. Admins and project owners can open every project they administer or own.
Endpoints
| Method | Endpoint | Description |
|---|---|---|
GET | /api/projects/{projectId}/members | List project members (ordered by first name, then last name) |
List Members
GET /api/projects/{projectId}/members
Returns every member of the project, each once: a user who is in two of the project's teams and also a direct member appears one time. Deleted users are left out. The list is not paginated. A project without members returns an empty array.
bash
curl https://{tenant}.kendo.dev/api/projects/1/members \
-H "Authorization: Bearer your-token"json
[
{
"id": 4,
"name": "Alice Visser",
"email": "[email protected]"
},
{
"id": 2,
"name": "Bob Aalbers",
"email": "[email protected]"
}
]Response Fields
| Field | Type | Description |
|---|---|---|
id | integer | User ID — pass it as assignee_id on an issue |
name | string | First name and last name, separated by a space |
email | string | The user's email address |
Error Responses
| Status | Cause |
|---|---|
401 | The request carries no valid token |
403 | The caller cannot access the project |
404 | No project exists with this ID |
See Also
- Issues API —
assignee_idtakes a member'sid - Projects API — The project the members belong to
- MCP Resources — The
project-membersresource returns the same members