Add a member or change the role (tenant:forge:write and project admin, or tenant:forge:admin)
PUT /api/forge/v1/projects/{key}/members/{ref}
Module: Forge · operationId: putForgeMember · Tag: Members · Auth: access token (Authorization: Bearer <accessToken>)
Requires tenant:forge:admin, or tenant:forge:write and project role admin. An owner, deputy or team member of an ownership keeps at least the developer role (409 in_use with details.counts.ownerships / details.counts.teams). Writes forge.project.saved.
Parameters
| Name | In | Type | Required | Description |
|---|---|---|---|---|
key |
path | string | yes | Project key (e.g. APP) |
ref |
path | string | yes | E-mail address of the person |
Request body
application/json (required)
role(Role, required): (one ofreporter,developer,maintainer,admin)
Example:
{
"role": "developer"
}
Responses
- 200 Member (
application/json) - 400 Error (
application/json) - 403 Error (
application/json) - 404 Error (
application/json)
Fields of the 200 answer:
addedAt(string (date-time), required): When the member was addedaddedBy(string, required): E-mail of who added the memberref(string, required): Lower-cased e-mail addressrole(Role, required): (one ofreporter,developer,maintainer,admin)
Example 200 answer:
{
"addedAt": "2026-09-23T09:05:00Z",
"addedBy": "emma.maier@muster-it.example",
"ref": "marie.wagner@muster-it.example",
"role": "developer"
}
Example request
curl -X PUT 'https://api.mbcom.cloud/api/forge/v1/projects/string/members/string' \
-H "Authorization: Bearer $ACCESS_TOKEN" \
-H 'Content-Type: application/json' \
--data '{"role":"developer"}'