kick_member
Kick a project member without banning them. Status rolls to churned; the subscriber can re-join later.
Purpose
Kick a project member without a permanent ban. Status rolls to churned; Telegram-side resource removal happens on the existing bot pipeline. The subscriber can re-join via a fresh purchase or access code later. Delegates to an Action so cache invalidation runs and member.kicked emits with the optional reason.
Required ability
project-user:update
Input schema
{
"type": "object",
"required": ["member_id"],
"properties": {
"member_id": {
"type": "string",
"description": "UUID of the project member to kick."
},
"reason": {
"type": "string",
"description": "Optional human-readable reason that lands in the member.kicked event payload."
}
}
}Output shape
{
"data": {
"id": "usr_01HX...",
"status": "churned"
}
}Example prompts
"Kick member
usr_01HX...for inactivity."
"Remove this subscriber's access but don't ban them."
Failure modes
RESOURCE_NOT_FOUND— unknownmember_id, or the member belongs to a team outside the token's scope.TOKEN_MISSING_ABILITY— token lacksproject-user:update.
Related
How is this guide?