Nasfam Business API docs
Guides and an API reference for delivering Telegram Stars and Premium to a Telegram username, from the quickstart to webhooks.
- A sandbox where a test username chooses the outcome, failures included
- Send yourself a signed test event, then replay any delivery
- Webhooks retried for about 3 days
- Check the recipient before you pay; a quote holds its price for 60 seconds
- An unconfirmed delivery is held and reviewed, never refunded on a timer
- We never ask for your Telegram or Fragment login, or a wallet seed
Where to start
What you can build
Sell Telegram Stars
Resolve a Telegram username and confirm the account found, lock the price for up to 60 seconds, then create the order and follow it until it finishes.
- POST /recipient-lookups
- POST /quotes
- POST /orders
Sell Telegram Premium
Resolve and confirm the recipient, quote a number of months, then create the order the same way.
- POST /recipient-lookups
- POST /quotes
- POST /orders
Fund your account with crypto
Read a deposit address of your own, simulate a deposit, and follow its state until it is credited.
- GET /funding/deposit-address
- GET /funding/deposits
Run on one prepaid balance
See what is available and what is held, and read every movement on the balance as a statement.
- GET /balance
- GET /balance/transactions
React when an order ends
Receive an event when an order succeeds, fails or goes under review, and read the same events from a 30-day log.
- POST /webhook-endpoints
- GET /events
Build with AI
These pages are written for you and for the assistant you work with. Hand it one page, or the whole documentation, in the form it reads best.
On every page
Copy pageOne press copies the page as Markdown, ready to paste into any assistant. The same control opens the page as a .md file.
Use with AIChoose your assistant. It opens in a new tab with a short prompt for that page already in it.
- ChatGPT
- Claude
- Perplexity
- Google AI
- Grok
- Cursor
You send itThe prompt points at the page and names your language and HTTP client. Nothing is sent for you. For your terminal, the prompt is copied to paste there.
- Claude Code
The same documentation, as files for your tools
- <page>.md
Any page as Markdown
Add .md to the address of a page and it answers as Markdown: the same headings, tables and code, with nothing to strip.
- llms.txt
The index
Every page with one line on what it holds, grouped by what you are trying to do. Where an assistant starts.
- llms-full.txt
The full text, in 21 files
An index of the full text: 21 files, one per task, each holding its pages whole, so an assistant loads the pages of the job in hand.
- openapi.json
The contract
OpenAPI: every operation, field and status. Import it into an API client or generate one from it.
- nasfam-business-api.postman_collection.json
A request collection
Every operation, for Postman, Bruno or Insomnia, with your test key as a variable it names. It holds no key.
- skill.md
Rules for a coding assistant
What an assistant must and must not do with this API, then the operations, the statuses and each topic in brief.
API fundamentals
- Authentication and keysOne bearer key per environment, sent on every request.
- Idempotency and safe retriesHow to retry any request, including one that changes your balance, without ever paying twice.
- ErrorsEvery error is a problem document with a stable code. Find a code, its usual cause and how to recover.
- Rate limitsWhat the API does when you send too much, and how to back off.
Latest changes
Contract, pinned on 2026-11-13
POST /recipient-lookups, the account found at a username, for your customer to confirm before you quote.recipient_lookupon a quote and an order, andfoundon a quote'srecipient.- Three event types:
order.accepted,order.refundedanddeposit.confirmed. - USD credits:
usd,headline,activityandspending_currencyonGET /balance,pay_withon a quote,conversionon a credited GRAM deposit andgram_conversionon the statement.
