Remove a user from an organization

DELETE/users/{user_id}

Remove a member from the organization. If the id is a PENDING user, their invitation is revoked instead. Requires a user credential (an API key is rejected) that is an Owner or Admin of the organization. Select a client organization with Organization-Id, or omit it for the partner firm team. You cannot remove yourself, and only an Owner can remove another Owner; either returns 403. Returns 404 if the organization is not accessible, or no such user or invitation exists; the response is empty on success.

Authorization

AuthorizationstringRequired

A signed-in user's session token, sent as Authorization: Bearer <token>. It authorizes the organizations that user can reach. Operations that manage people accept only this credential; operations on data also accept an API key.

Headers

Api-Versiondate

Release date, as YYYY-MM-DD. Defaults to 2026-07-21.

Organization-Idstring

Target client organization. Omit to manage the partner firm team when the bearer is an Owner or Admin of exactly one portfolio.

Connection-Idstring

Target connection id; resolves to its organization.

Entity-Idstring

Platform entity id; resolves to a connection's organization.

Entity-Sourcestring

Optional source to disambiguate an Entity-Id.

Path parameters

user_idstringRequired

Opaque identifier of the user to remove. Treat as opaque.

Response

204

Successful Response

400

The request was invalid.

401

Authentication failed or was missing.

403

The credential is not permitted for this request.

404

The requested resource was not found.

422

The request failed validation.

503

A service this request depends on was unavailable. Retry the request.

cURL

DELETE /users/{user_id}

-H "Authorization: Bearer ***"

-H "Api-Version: 2026-07-21"

Example request

https://api.trykintsugi.com/users/{user_id}

Response

{

"code": "invalid_request",

"message": "The user could not be removed from the organization.",

"requestId": "req_8f3k2mNpQr7Ls",

"errors": []

}