Telegram Membership API for AI Agents and Integrations
Every KickThemBot plan, Fresh included, has API access. AI agents use the owner API to set up and run an account for its owner, and website checkouts, support tools and CRMs use a project key.
API on every planOwner API for AI agentsAccess-code creationMembership lookup
Owner API for AI agents
An agent pairs with the owner through an Approve tap in @KickThemBot and receives a scoped owner token. It can read the plan with GET /api/me, create a plan checkout link, projects, chat admin links, plans, access codes and a Telegram link for the owner to connect Stripe in @KickThemBot, and check setup-status. Member records and project API keys need Sensitive permissions the owner approves separately. The OpenAPI 3.1 contract is at https://api.kickthembot.com/openapi.json.
Pairing approved in Telegram
Scoped, revocable owner token
Human steps returned with a ready message
Project keys for your own systems
A project API key covers one project and stays on trusted servers. It is meant for backend integrations such as a website checkout or a CRM, not public frontend code.
Bearer or API-key style auth
Project-level scope
Server-side storage
Provision access after website payment
A website checkout can create an access code with the plan, buyer identity, and duration after payment confirmation.
List plans
Create access code
Send code or access link to buyer
Look up membership status for support
Support and CRM systems can use membership lookup to answer whether a customer is active, expired, cancelled, or currently entitled to access.
Lookup by supported identifiers
Read plan and expiry
Update renewals where supported
Access lifecycle
How KickThemBot turns Telegram membership API into an operating workflow.
Every paid membership in KickThemBot follows the same path: a payment, the member's Telegram account, a visible status and removal when access ends.
01 / Payment source
Start from a real payment
A Stripe checkout on your own account, or an access code you send after a crypto, invoice or partner sale, starts the membership.
02 / Telegram identity
Know who has access
The membership belongs to the Telegram account that paid or redeemed the code, and each invite link holds one member at a time.
03 / Access status
See every member
In the Mini App, admins search members, see each plan, status, end date and source, and extend or remove access.
04 / Expiry outcome
End access cleanly
Reminders go out before the end date, subscriptions get a short renewal grace, and the bot removes members when access ends.
Project access routeReady
Payment or codeMember recordedInvite link sentExpiry tracked