Skip to main content
Member and invitation endpoints let you query who has access to your workspaces and control team membership programmatically. Members are users who have accepted an invitation and joined the workspace. Invitations represent pending access grants that have not yet been accepted. All requests require your API key in the Authorization header as Bearer <your_api_key>.

List workspace members

GET https://api.chevre.io/v1/workspaces/{workspace_id}/members Returns an array of all active members in the specified workspace. Pending invitations that have not yet been accepted are not included — use the List invitations endpoint for those.

Path parameters

workspace_id
string
required
The unique identifier of the workspace whose members you want to list (e.g. ws_01HXYZ).

Example request

Example response

200

Response fields

data
array
An array of member objects for the workspace.

Invite a user

POST https://api.chevre.io/v1/workspaces/{workspace_id}/invitations Sends an email invitation to the specified address, granting the recipient access to the workspace with the given role when they accept. If the email address already belongs to an active member of the workspace, the request returns a 409 Conflict error.
Invitations expire after 7 days. If the recipient does not accept within that window, you will need to send a new invitation. You can monitor invitation status using the status field on the invitation object.

Path parameters

workspace_id
string
required
The unique identifier of the workspace to invite the user into (e.g. ws_01HXYZ).

Request body

email
string
required
The email address of the person you want to invite. Must be a valid email format.
role
string
required
The role to assign to the user when they accept the invitation. Accepted values:
  • "owner" — full administrative control, including billing and workspace deletion.
  • "admin" — can manage members, projects, and all workspace settings.
  • "editor" — can create and edit projects and automations, but cannot manage members.
  • "viewer" — read-only access to all shared projects in the workspace.

Example request

Example response

201

Response fields

data
object
The newly created invitation object.

Update a member’s role

PATCH https://api.chevre.io/v1/workspaces/{workspace_id}/members/{member_id} Updates the role of an existing workspace member. You must have admin or owner permissions in the workspace to update member roles. An owner cannot downgrade their own role — another owner must perform that action.

Path parameters

workspace_id
string
required
The unique identifier of the workspace (e.g. ws_01HXYZ).
member_id
string
required
The unique identifier of the member whose role you want to update (e.g. mem_02STU).

Request body

role
string
required
The new role to assign to the member. Accepted values: "owner", "admin", "editor", or "viewer".

Example request

Example response

200

Response fields

data
object
The updated member object.

Remove a member

DELETE https://api.chevre.io/v1/workspaces/{workspace_id}/members/{member_id} Removes a member from the workspace, immediately revoking their access to all projects and data within it. The removed member’s account is not deleted — they simply lose access to this workspace.
Removing a member immediately revokes their access. Any automations or tasks assigned to the removed member will remain but become unassigned. This action cannot be undone — you must send a new invitation if you want to restore their access.

Path parameters

workspace_id
string
required
The unique identifier of the workspace (e.g. ws_01HXYZ).
member_id
string
required
The unique identifier of the member to remove (e.g. mem_02STU).

Example request

Example response

204
A successful removal returns HTTP 204 No Content with an empty response body.