Member

The member represents a user in the scope of a specific organisation. It contains the user reference, to role of the user within the organisation and some member specific metadata. A member can be created by two distinct scenarios:

• A user applies for a membership which then is approved or rejected by the organisation
• The organisation explicitly makes a user a member

Endpoints

For information only. Full, normative endpoint definitions in the Swagger documentation.

Example Member datatype

{
		"type": "MEMBER",
		"id": "979719aa-68aa-40ef-9fd9-735901510b07",
		"orgId": "f306a329-2911-48c4-917c-a5e70958be15",
		"role": "orgadmin",
		"userRef": "73646882-e0f1-7085-ada2-f257f7a4cb1d",
		"createdAt": "2025-06-17T13:01:04.296Z",
		"createdBy": {
			"userId": "73646882-e0f1-7085-ada2-f257f7a4cb1d"
		},
		"firstName": "Milla",
		"lastName": "BECA"
	}

The Member resource represents a user within the scope of a specific organisation. It links a user to an organisation with a role and member-specific metadata.

Member Lifecycle

A member can be created in two ways:

1. User-initiated: A user applies for membership in an organisation. The application becomes a pending member and must be approved or rejected by an organisation admin.
2. Organisation-initiated: An organisation admin explicitly creates a member for a given user.

Core Behaviour by Endpoint

• GET /orgs/:orgId/members/pending
• GET /orgs/:orgId/members
• POST /orgs/:orgId/members
• PUT /orgs/:orgId/members/approve
• PUT /orgs/:orgId/members/reject
• GET /orgs/:orgId/members/:memberId
• PUT /orgs/:orgId/members/:memberId
• DELETE /orgs/:orgId/members/:memberId

Example Member Object

{

“type”: “MEMBER”,

“id”: “979719aa-68aa-40ef-9fd9-735901510b07”,

“orgId”: “f306a329-2911-48c4-917c-a5e70958be15”,

“role”: “orgadmin”,

“userRef”: “73646882-e0f1-7085-ada2-f257f7a4cb1d”,

“createdAt”: “2025-06-17T13:01:04.296Z”,

“createdBy”: {

"userId": "73646882-e0f1-7085-ada2-f257f7a4cb1d"