EaserixDocs
DevelopersAPI referenceAuth & accountsTeams

Team members

Any workspace member. Same row shape as the workspace directory; role is lead | member.

View as Markdown
GET
/v1/workspaces/{id}/teams/{tid}/members

Authorization

bearer
AuthorizationBearer <token>

In: header

Path Parameters

id*string
tid*string

Response Body

application/json

application/json

application/json

application/json

curl -X GET "https://example.com/v1/workspaces/string/teams/string/members"
{  "members": [    {      "user_id": "a169451c-8525-4352-b8ca-070dd449a1a5",      "email": "string",      "name": "string",      "avatar_url": "string",      "role": "string",      "joined_at": "2019-08-24T14:15:22Z"    }  ]}

Delete a team

Team workspaces only; team lead or org.teams.manage. Soft delete. The workspace's DEFAULT team cannot be deleted and answers 409 with `code: default_team`. Everyone who joins the workspace belongs to it, so deleting it dropped every roster row, left the team's content unreachable in the tools, and was then rebuilt empty by the next join — carrying only the owner and that joiner, leaving everyone else on no team until the service next converged. An admin tightening access wants to remove members, which is a different call. The default team goes when the workspace goes.

Add a team member

Team workspaces only; team lead or org.teams.manage. Target must already be a workspace member (400, not 404, otherwise). Upserts the role.