> For the complete documentation index, see [llms.txt](https://docs.tomoads.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tomoads.com/for-publishers/telegram-mini-app-verification.md). # Telegram Mini App Requirements This page describes publisher-facing requirements for Telegram Mini App style inventory. ## Why This Exists TomoAds applies additional checks for Telegram-context traffic to maintain quality and trust. ## What Publishers Must Provide * correct bot identity details during setup * accurate property configuration * valid integration setup in their Mini App environment If automatic bot identity resolution is unavailable, dashboard may request manual bot ID entry. ## Expected Integration Behavior * requests should originate from actual Telegram Mini App context * integration parameters must remain fresh and valid * normal anti-abuse and policy checks still apply ## What to Avoid * sharing tracking URLs outside intended Telegram flows * synthetic or incentivized click schemes * mismatched bot/property metadata ## Important Note Passing Telegram context checks does not override platform quality policies. Traffic quality and advertiser value remain core requirements for long-term eligibility and payouts. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.tomoads.com/for-publishers/telegram-mini-app-verification.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.