Removes a person from your organization. Their API keys are revoked and their shared credentials are withdrawn from the org before the roster entry is dropped.

If the address has a pending invitation rather than a membership, the invitation is revoked — data.removed says which happened.

Check data.warnings. Removal is never blocked, so anything of theirs the org was relying on is affected: workflows using a connection they owned start failing, active sources they owned stop importing, and workflows they still own keep running — scheduled runs charge the owner, so the org keeps paying for them. Each warning names the affected resources so you can reassign them. An empty array means none of those checks found anything, not that the member was inconsequential.

Requires the members:write scope, which only an org admin's API key can carry. You cannot remove yourself.

Percent-encode the address: a literal + in a query string decodes to a space, so sam+team@acme.com must be sent as sam%2Bteam%40acme.com.

Refusals carry a code: