Members

List the active members of the organization

GET

https://api.lelemon.cl

/v2/members

Bearer (API key)

Use it to find the mbr_ id that POST /v2/cases/{id}/assign takes as assigneeId, and to see who is available. Read only: it does not invite, change roles, change the case scope or set availability. It returns the case scope of each member. Suspended and invited members are not listed. Newest first.

Required scope: members:read.

List the active members of the organization › query Parameters

limit

integer · min: 1 · max: 100

Default: 20

cursor

string · maxLength: 512

The nextCursor of the previous page, with the same filters.

List the active members of the organization › Headers

Lelemon-Subaccount

string · pattern: ^sub_[0-9A-Za-z]{22}…

The subaccount (sub_…) this request acts on. Only for the keys of a platform account; without it the request acts on the account itself.

List the active members of the organization › Responses

MemberList

object

string · enum · required

Enum values:

list

hasMore

boolean · required

nextCursor

string | null · required

Member[] · required

List who invited, changed the role of or removed members

GET

https://api.lelemon.cl

/v2/members/audit-log

Bearer (API key)

The audit log of members, newest first: invitations created, resent and cancelled, role changes and removals, with who did it (the member and the API key, if it came from one), to whom, and the role before and after. Filter with member to see only what was done to one member, their invitation included. Read only. It needs members:audit-read, which only an admin or the owner can give.

Required scope: members:audit-read.

List who invited, changed the role of or removed members › query Parameters

limit

integer · min: 1 · max: 100

Default: 20

cursor

string · maxLength: 512

The nextCursor of the previous page, with the same filters.

member

string

Only what was done to this member, including their invitation. Same id as members.list.

List who invited, changed the role of or removed members › Headers

Lelemon-Subaccount

string · pattern: ^sub_[0-9A-Za-z]{22}…

The subaccount (sub_…) this request acts on. Only for the keys of a platform account; without it the request acts on the account itself.

List who invited, changed the role of or removed members › Responses

MemberAuditList

object

string · enum · required

Enum values:

list

hasMore

boolean · required

nextCursor

string | null · required

MemberAuditEntry[] · required

GET/v2/members/audit-log

curl https://api.lelemon.cl/v2/members/audit-log \
  --header 'Authorization: Bearer <token>'

Example Responses

{
  "object": "list",
  "hasMore": true,
  "nextCursor": "nextCursor",
  "data": [
    {
      "object": "member_audit_entry",
      "id": "mae_4Zq0x8bVw1TqS9mYp3RkLd",
      "action": "invitation.created",
      "actor": {
        "memberId": "mbr_4Zq0x8bVw1TqS9mYp3RkLd",
        "apiKeyId": "key_4Zq0x8bVw1TqS9mYp3RkLd"
      },
      "target": {
        "memberId": "mbr_4Zq0x8bVw1TqS9mYp3RkLd",
        "invitationId": "inv_4Zq0x8bVw1TqS9mYp3RkLd",
        "email": "[email protected]"
      },
      "roleBefore": "owner",
      "roleAfter": "owner",
      "scopeBefore": "all",
      "scopeAfter": "all",
      "createdAt": "2024-08-25T15:00:00Z"
    }
  ]
}

json

application/json

Read whether a team member is available

GET

https://api.lelemon.cl

/v2/members/{id}/availability

Bearer (API key)

status is what was marked; availableForAssignment says whether the assignment would give them a new case now, considering the opening hours of the organization. Read only and safe to repeat.

Required scope: members:read.

Read whether a team member is available › path Parameters

id

string · pattern: ^mbr_[0-9A-Za-z]{22}… · required

The id of the member (mbr_…).

Read whether a team member is available › Headers

Lelemon-Subaccount

string · pattern: ^sub_[0-9A-Za-z]{22}…

The subaccount (sub_…) this request acts on. Only for the keys of a platform account; without it the request acts on the account itself.

Read whether a team member is available › Responses

MemberAvailability

object

string · enum · required

Enum values:

member_availability

memberId

string · required

email

string · required

status

string · enum · required

What was marked, by the person or by the API. It does not consider the opening hours of the organization: that is availableForAssignment.

Enum values:

available

away

availableForAssignment

boolean · required

Whether the assignment would give this person a new case right now. false if away, and also if available but the organization has opening hours and they are closed: the automatic away by schedule wins, unless the person asked to keep going a while longer (extendedUntil in the future).

changedAt

string | null · date-time · required

When the status last changed. null if it never did.

extendedUntil

string | null · date-time · required

Until when the person asked to keep receiving cases after the opening hours. null if there is no extension.

Mark a team member available or away

PUT

https://api.lelemon.cl

/v2/members/{id}/availability

Bearer (API key)

Does the same as when the person changes their own status: the assignment of new cases reads it from there. away takes them out of the assignment and drops the extension they asked for. available marks them, but if the organization has opening hours and they are closed, the automatic away by schedule still wins (availableForAssignment stays false) unless the person asked to keep going a while longer. Setting the status they already have writes nothing, so repeating the request is safe. It needs members:write: members:read does not include it.

Required scope: members:write.

Mark a team member available or away › path Parameters

id

string · pattern: ^mbr_[0-9A-Za-z]{22}… · required

The id of the member (mbr_…).

Mark a team member available or away › Headers

Lelemon-Subaccount

string · pattern: ^sub_[0-9A-Za-z]{22}…

The subaccount (sub_…) this request acts on. Only for the keys of a platform account; without it the request acts on the account itself.

Mark a team member available or away › Request Body

SetMemberAvailability

status

string · enum · required

available: can receive new cases. away: the assignment skips them and any extension they asked for is dropped.

Enum values:

available

away

Mark a team member available or away › Responses

MemberAvailability

object

string · enum · required

Enum values:

member_availability

memberId

string · required

email

string · required

status

string · enum · required

What was marked, by the person or by the API. It does not consider the opening hours of the organization: that is availableForAssignment.

Enum values:

available

away

availableForAssignment

boolean · required

changedAt

string | null · date-time · required

When the status last changed. null if it never did.

extendedUntil

string | null · date-time · required

Until when the person asked to keep receiving cases after the opening hours. null if there is no extension.

Change the role of a member

PATCH

https://api.lelemon.cl

/v2/members/{id}/role

Bearer (API key)

Same rule as the panel, capped by the current role of whoever issued the key: it never gives a role above that role, never touches someone with a higher role, and the owner is never changed nor named by API. The owner can set admin, member or viewer; an admin only member or viewer, and only on members and viewers. It is recorded in the audit log of members with the key. It needs members:manage.

Required scope: members:manage.

Change the role of a member › path Parameters

id

string · pattern: ^mbr_[0-9A-Za-z]{22}… · required

The id of the member (mbr_…).

Change the role of a member › Headers

Lelemon-Subaccount

string · pattern: ^sub_[0-9A-Za-z]{22}…

The subaccount (sub_…) this request acts on. Only for the keys of a platform account; without it the request acts on the account itself.

Change the role of a member › Request Body

UpdateMemberRole

role

string · enum · required

The new role. It cannot be above the current role of whoever issued the key, and nobody is named owner by API.

Enum values:

admin

member

viewer

Change the role of a member › Responses

Member

object

string · enum · required

Enum values:

member

id

string · required

The id that POST /v2/cases/{id}/assign takes as assigneeId.

name

string | null · required

email

string · required

role

string · required

The role of the member. A viewer cannot be assigned cases.

availability

string · enum · required

Whether the member is receiving new cases right now.

Enum values:

available

away

caseScope

string | null · enum · required

Which cases the member sees, when set for them: all (every case of their pipelines), unassigned_and_own (the unassigned ones and theirs) or assigned (only theirs). null means they follow the default of the organization.

Enum values:

all

unassigned_and_own

assigned

effectiveCaseScope

string · enum · required

What the member sees now: caseScope, or the default of the organization when that is null. The owner and admins always see all. The MCP connector of Lelemon only works for people who see all.

Enum values:

all

unassigned_and_own

assigned

createdAt

string · date-time · required

Change which cases a member sees

PATCH

https://api.lelemon.cl

/v2/members/{id}/case-scope

Bearer (API key)

Same rule as the Team screen of the panel, capped by the current role of whoever issued the key: it never touches someone with a higher role (an admin changes members and viewers only), and the owner and admins always see all, so their scope cannot be set. caseScope all lets the person see every case of their pipelines, which is also what the MCP connector of Lelemon requires; null goes back to the default of the organization. Setting the value they already have writes nothing, so repeating the request is safe. It is recorded in the audit log of members with the key. It needs members:manage.

Required scope: members:manage.

Change which cases a member sees › path Parameters

id

string · pattern: ^mbr_[0-9A-Za-z]{22}… · required

The id of the member (mbr_…).

Change which cases a member sees › Headers

Lelemon-Subaccount

string · pattern: ^sub_[0-9A-Za-z]{22}…

The subaccount (sub_…) this request acts on. Only for the keys of a platform account; without it the request acts on the account itself.

Change which cases a member sees › Request Body

UpdateMemberCaseScope

caseScope

string | null · enum · required

all: sees every case of their pipelines. unassigned_and_own: the unassigned ones and theirs. assigned: only theirs. null: goes back to the default of the organization.

Enum values:

all

unassigned_and_own

assigned

Change which cases a member sees › Responses

Member

object

string · enum · required

Enum values:

member

id

string · required

The id that POST /v2/cases/{id}/assign takes as assigneeId.

name

string | null · required

email

string · required

role

string · required

The role of the member. A viewer cannot be assigned cases.

availability

string · enum · required

Whether the member is receiving new cases right now.

Enum values:

available

away

caseScope

string | null · enum · required

Enum values:

all

unassigned_and_own

assigned

effectiveCaseScope

string · enum · required

What the member sees now: caseScope, or the default of the organization when that is null. The owner and admins always see all. The MCP connector of Lelemon only works for people who see all.

Enum values:

all

unassigned_and_own

assigned

createdAt

string · date-time · required

Remove a member from the organization

DELETE

https://api.lelemon.cl

/v2/members/{id}

Bearer (API key)

The person loses access and leaves their teams. The keys they issued lose their power to manage on the next call. Capped by the current role of whoever issued the key: an admin removes members and viewers only, and the owner is never removed by API. It is recorded in the audit log of members with the key. It needs members:manage.

Required scope: members:manage.

Remove a member from the organization › path Parameters

id

string · pattern: ^mbr_[0-9A-Za-z]{22}… · required

The id of the member (mbr_…).

Remove a member from the organization › Headers

Lelemon-Subaccount

string · pattern: ^sub_[0-9A-Za-z]{22}…

The subaccount (sub_…) this request acts on. Only for the keys of a platform account; without it the request acts on the account itself.

Remove a member from the organization › Responses

Removed.

No data returned

Budgets Invitations