Remove a member, or leave

DELETE

/v1/members/{id}

curl --request DELETE \
  --url https://beta-api.plune.ai/v1/members/example \
  --header 'Authorization: Bearer <token>'

• beta
• production
• local

An owner removes anybody; a member removes only themself — that is “Leave” (api.ts → removeMember). Their records stay: a case somebody wrote is the project’s, not theirs. The last owner can do neither (409). A reader cannot leave — the read-only rule has no exceptions, so an owner removes them. Recorded in the audit feed as removed <email> or <email> left.

Authorizations

• bearerAuth
• cookieAuth

Parameters

Path Parameters

id

required

string

The member’s userId — your own to leave

Header Parameters

X-Plune-Project

string

Which of your projects to act in — an id from GET /v1/projects. Absent, your default project. A project you are not a member of answers 404, the same as one that does not exist. Ignored under a bearer token, which is bound to the project it was minted in.

Responses

204

Removed

401

No / invalid token or session

403

A member asked about somebody else, or a reader asked at all

Media type application/json

object

error

required

string

Example

{
  "error": "project owner only"
}

404

No such member in this project

Media type application/json

object

error

required

string

Example ^generated

{
  "error": "example"
}

409

The last owner

Media type application/json

object

error

required

string

Example

{
  "error": "a project needs an owner — make somebody else one first"
}

429

Rate-limited: either the per-route throttle or a tenant quota. Retry-After carries the seconds until the window rolls over.

Media type application/json

object

error

required

string

Example ^generated

{
  "error": "example"
}

Headers

Retry-After

integer

Seconds until the window rolls over