Skip to main content

Lowest-cost Telegram Stars and Premium API for Fragment.com - KYC 0%, no-KYC 0.25%, TON/USDT

Project description

Fragment Stars API

THE CHEAPEST FRAGMENT API

KYC 0% · NO-KYC 0.25%

Public rates. No API key. Verify anytime with GET /api/v1/commission/rates.

Telegram Stars API for Fragment.com
Buy Telegram Stars and Premium from your backend with Python SDK or direct REST.
No API key. KYC 0% forever. No-KYC only 0.25%. TON + USDT on TON.

PyPI version Python versions Documentation website Like it? Star it! MIT License

Quick Start · Minimal Shop · REST API · KYC vs No-KYC · Example Shop · RU

Lowest-cost Telegram Stars API for Fragment.com with KYC 0% and no-KYC 0.25%

What You Get

No API key
Client endpoints accept JSON directly. No issued token, JWT, OAuth, or X-API-Key.
Lowest API fees
0% KYC forever and only 0.25% without KYC. Verify with get_rates().
TON + USDT
Use default ton or pass usdt_ton where supported.
SDK + REST
Python package plus raw HTTP examples for Node.js, PHP, Go, and any backend.

Start Here

If you need to... Open this
Build a Telegram Stars shop Minimal backend and shop guide
Copy raw HTTP calls REST API guide and direct REST example
Choose KYC or no-KYC KYC vs No-KYC guide
Debug an API error Errors guide
Let Codex or Claude integrate it Codex skill / Claude skill
Ask for help Integration Help issue or @makecodev

Production Endpoint

https://fragment-api.ydns.eu:8443
curl https://fragment-api.ydns.eu:8443/health

Client endpoints do not require Authorization, X-API-Key, JWT, OAuth, or issued API tokens. The API tracks commission by the TON wallet derived from the provided seed. Internal admin endpoints are separate and are not needed for client integrations.

Quick Start

pip install fragment-stars-api
from fragment_api import FragmentAPIClient

client = FragmentAPIClient("https://fragment-api.ydns.eu:8443")

result = client.buy_stars(
    username="@telegram_user",
    amount=100,
    seed="your_wallet_seed_base64",
    payment_method="ton",
)

if result.success:
    print(f"Sent {result.amount} Stars")
    print(result.transaction_hash or result.transaction_id)
else:
    print(result.error)

Build a Telegram Stars Shop in 10 Minutes

  1. Install the SDK on your backend.
  2. Store FRAGMENT_WALLET_SEED in backend environment variables only.
  3. Accept username and amount from your bot/shop.
  4. Call client.buy_stars("@telegram_user", amount, seed=...).
  5. Return the final status to your user.

Runnable minimal backend:

pip install fastapi uvicorn fragment-stars-api
export FRAGMENT_WALLET_SEED="base64_seed_phrase"
uvicorn examples.shop_minimal:app --host 0.0.0.0 --port 8000

Full guide: docs/telegram-stars-shop.md. Production-ready shop example: bbbuilt/tg_stars_premium_shop.

Use Cases

Use case Recommended path
Telegram Stars shop or bot Use buy_stars() from backend and poll queue automatically with SDK.
KYC user has Fragment cookies Pass fragment_cookies / cookies; API commission stays 0%.
Client does not want cookies Omit cookies and use no-KYC mode.
Client wants USDT pricing Pass payment_method="usdt_ton" for supported Stars flows.
Non-Python stack Use direct REST endpoints; no API key is needed.
AI/vibe coding integration Add CODEX_SKILL.md or CLAUDE_SKILL.md to the client project first.

KYC vs No-KYC

Mode Cookies required API commission Good for
KYC Yes, user's Fragment cookies 0% forever Lowest cost, users comfortable with Fragment cookies
No-KYC No 0.25% Fast onboarding, shops that do not want user cookies

KYC can use ton or usdt_ton. No-KYC Stars can use ton or usdt_ton; with USDT, Stars base price is paid in USDT on TON and API commission is paid in TON. More detail: docs/no-kyc-vs-kyc.md.

Python SDK vs Direct REST

Option Best for Example
Python SDK Python bots, FastAPI, Django, background workers examples/payment_methods.py
Direct REST Node.js, PHP, Go, Laravel, Java, Rust, custom backends docs/rest-api.md
Minimal shop backend Fastest copy-paste backend start examples/shop_minimal.py

Runnable Examples

API Reference

Direct HTTP Endpoints

Send JSON only. No API key or auth header is required.

Method Path Purpose Required JSON
POST /api/v1/stars/buy Buy Stars through the queue username, amount, seed
GET /api/v1/queue/{request_id} Poll a Stars request none
POST /api/v1/premium/buy Buy Premium username, duration, seed
POST /api/v1/premium/check-eligibility Check Premium availability username
GET /api/v1/prices Get TON and USDT-on-TON prices none
GET /api/v1/commission/rates Check commission rates none

Optional purchase fields: fragment_cookies, fragment_local_storage, payment_method. Default payment_method is ton; use usdt_ton for USDT on TON where supported.

FragmentAPIClient

FragmentAPIClient(
    base_url: str,
    timeout: float = 30.0,
    poll_timeout: float = 300.0,
)
Method Description
buy_stars(username, amount, seed, cookies?, local_storage?, payment_method?, wait?) Buy Telegram Stars through the queue
buy_premium(username, duration, seed, cookies?, local_storage?, payment_method?, wait?) Buy Telegram Premium directly
get_prices() Get current TON and USDT-on-TON prices
get_rates() Get commission rates
get_queue_status() Get queue status and statistics
check_premium_eligibility(username) Check if user is eligible for Premium
get_status(request_id) Get request status

Common Client Mistakes

Mistake Correct approach
Asking for an API token Do not use API tokens for client endpoints. Send JSON to the production endpoint.
Sending seed from frontend Keep seed and cookies on backend only. Never expose them in a browser or mobile app.
Retrying blindly after an uncertain transaction Check wallet/TON explorer first. A blind retry can duplicate purchases.
Passing username without @ in direct REST Use @telegram_user format unless your SDK normalizes it.
Using KYC without stel_ton_token Connect wallet on Fragment first, then export cookies.

Full troubleshooting: docs/errors.md.

Common Errors

Error Meaning What to do
VALIDATION_ERROR Bad request body, wrong username format, unsupported amount or payment method Fix the request; usernames should look like @telegram_user.
INVALID_SEED / INVALID_WALLET_SEED Wallet seed is missing, malformed, or not base64 encoded correctly Re-encode the 24-word seed on the backend.
INSUFFICIENT_BALANCE / INSUFFICIENT_WALLET_BALANCE Wallet has too little TON, USDT on TON, or gas balance Top up the wallet before creating a new request.
USER_NOT_FOUND / TELEGRAM_USER_NOT_FOUND Fragment could not find the Telegram user Check the username and try a new request.
FRAGMENT_ADDITIONAL_VERIFICATION_REQUIRED Fragment asks the account for extra verification Open Fragment manually with that account/cookies and complete the check.
TEMPORARY_FRAGMENT_CONNECTION_ERROR Temporary connection problem between the API server and Fragment.com Submit a new request later. Do not reuse the old request_id.
TEMPORARY_FRAGMENT_FORM_NOT_READY Fragment page or form did not become ready in time Submit a new request later.
TON_TRANSACTION_CONFIRMATION_UNCERTAIN Transaction signing/sending may be uncertain Check the wallet/TON explorer before retrying.

Fragment Cookies for KYC Mode

KYC mode requires Fragment.com cookies and has 0% API commission permanently.

Required cookies:

  • stel_token
  • stel_ssid
  • stel_ton_token
  • stel_dt

Read the full guide: COOKIES_GUIDE.md. If you do not want to handle cookies, use no-KYC mode by omitting the cookies parameter.

Vibe Coding / AI Agent Setup

If a client integrates with Codex, Claude, Cursor, or another AI coding agent, give the agent a ready-made skill file first. It prevents invented API tokens, frontend seed leaks, cookie leaks, and duplicate purchases from blind retries.

Need Help Integrating?

Contributing

Issues and integration feedback are welcome. See CONTRIBUTING.md and SECURITY.md. Do not post wallet seeds, Fragment cookies, private keys, or production customer data in public issues.

Author

Basebay - backend developer focused on automation, bots, and infrastructure tools.

License

MIT License - see LICENSE.

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

fragment_stars_api-2.1.2.tar.gz (828.0 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

fragment_stars_api-2.1.2-py3-none-any.whl (13.6 kB view details)

Uploaded Python 3

File details

Details for the file fragment_stars_api-2.1.2.tar.gz.

File metadata

  • Download URL: fragment_stars_api-2.1.2.tar.gz
  • Upload date:
  • Size: 828.0 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.2.0 CPython/3.13.3

File hashes

Hashes for fragment_stars_api-2.1.2.tar.gz
Algorithm Hash digest
SHA256 862fc02ef5a61a4b744de1f10a57ef930ca2b9ce59ec67fbb06d491a14241bd2
MD5 dcb2786882c7fe95a543602cf2b5b848
BLAKE2b-256 820136b0d5de9741305cf46030f340c1d26d9422508881f17dbc61bc05e5ab74

See more details on using hashes here.

File details

Details for the file fragment_stars_api-2.1.2-py3-none-any.whl.

File metadata

File hashes

Hashes for fragment_stars_api-2.1.2-py3-none-any.whl
Algorithm Hash digest
SHA256 378eb5d5f0c3ea7e7b8b6e99efa2775f3b620733d4242d80f78003e82a49d375
MD5 aee7b04f8b87ae81118dbadee2d1ec40
BLAKE2b-256 5f1b6ed6e37a49270ffe108872c61bad2e7e034bea63c922832c42b1c2542409

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page