Skip to main content
DELETE
Removes one person from your organisation. Their account is not deleted, and any other organisation they belong to is unaffected. Removing someone takes their access with it, straight away:
  • They are signed out of the console on every device, and their sign-ins to the other surfaces (Chat, Agents, the Gateway) can no longer be renewed through MITHUNAI. A session already open on one of those may run until it next needs renewing.
  • Every API key they created in your organisation is revoked. Anything using one of those keys stops working, so check the keys list first if a key they made is in use. See Managing API keys.
  • Every invitation they sent that has not been accepted is withdrawn.
The response tells you how many keys and invitations were affected. This endpoint takes a signed-in console session, not an API key. Send the session cookies your browser received when you signed in, plus the X-CSRF-Token header set to the value of the csrf_token cookie. A request authenticated with an mithunai_sk_ key is refused with 403. You need the owner or admin role. You cannot remove yourself (403), someone more senior than you (403), or the organisation’s owner (409). A member who does not exist, a member of another organisation and a malformed ID all return the same 404. To bring someone back, invite them again. See Members.
string
required
The member’s account ID (UUID), as returned in account_id by List members.
string
required
The value of your session’s csrf_token cookie (named __Host-csrf_token when the console is served over HTTPS without a shared cookie domain). A missing or mismatched token returns 401.

Response

boolean
required
Always true.
string
required
The account ID of the person removed.
integer
required
How many API keys they created in this organisation were revoked.
integer
required
How many invitations they sent were withdrawn.
Last modified on November 7, 2026