patch · projects:write

Update member role

Update member role

WriteIdempotent

REST

patch/api/v1/members/{id}
curl "https://herculeradar.com/api/v1/members/:id" \
  --request PATCH \
  --header "Authorization: Bearer hr_live_…" \
  --header "Content-Type: application/json" \
  --header "Idempotency-Key: $(uuidgen)" \
  --data '{"role":"editor"}'

MCP

Tool name update_project_member. It takes the same input and returns the same { data, meta } envelope as REST, because both call the same function.

Change a member between viewer and editor.

Parameters

idrequiredstringUser id

Request body

{
  "type": "object",
  "required": [
    "role"
  ],
  "properties": {
    "role": {
      "type": "string",
      "enum": [
        "editor",
        "viewer"
      ]
    }
  }
}

Response

{
  "data": {
    "user_id": "uuid",
    "role": "editor"
  },
  "meta": {
    "capability": "update_project_member",
    "requestId": "req_9f2b4a8c1d0e",
    "idempotencyReplayed": false,
    "docs": "https://herculeradar.com/docs/reference/update_project_member"
  }
}

Authorization

Requires the projects:write scope. A credential without it gets 403 FORBIDDEN. Resources in projects the credential cannot reach answer 404 NOT_FOUND rather than 403, so ids cannot be probed across tenants.

Send an Idempotency-Key header. A completed response is replayed for 24 hours, so a retry after a timeout cannot create a duplicate.