Format the identifier first
Send one number in E.164 form with its country code, for example +17253100591.
Synchronous Telegram API
Submit one number and know instantly whether it is on Telegram. The SaaS dashboard answers on the spot; the synchronous REST API returns JSON in the same response.

POST /api/v1/demo/checkNo sign-in required.
Quickstart
Check contract
Send one number in E.164 form with its country code, for example +17253100591.
The registration check (tg) returns registration status in the registered field.
Single and multi checks return JSON in the same response for your workflow to read immediately.
Verification product
Use cases
Check a newly captured number before creating a CRM record, assigning an owner, or starting a consent-aware follow-up.
Add the Telegram registration result while a CRM, sales, or support record is created, reviewed, or updated.
Use the synchronous response in backend rules or support tools when the next action depends on a current Telegram signal.
Latest guides
Practical articles on Telegram checks, API integration, and verification workflows.

Understand carrier and line-type data, mobile portability, and platform reachability signals to improve routing and message delivery workflows.
Read article
Learn what a silent platform registration check is, how it differs from carrier authentication, and how teams use registration signals in data workflows.
Read article
Learn what an HLR lookup is, what network data it reveals, and how it differs from messaging platform registration checks in technical workflows.
Read article
Explore what phone number line type means across mobile, landline, and VoIP networks, and how it informs messaging and reachability workflows.
Read article
Learn how pre-campaign phone number verification and Telegram registration signals help teams refine list hygiene, segment outreach, and reduce waste.
Read article
Learn what E.164 phone number format is, how it is structured up to 15 digits, and why digital verification APIs require it for accurate normalization.
Read articleFAQ
Answers on Telegram registration, balance, API access, and failed validations.
Submit one number and TG Validator returns whether it is registered on Telegram in the same response: the tg product returns the registered field. There is no task queue, no polling and no callbacks. Message content is never checked.
Yes. Once a number is submitted, the result comes back in the same HTTP response — no task queue, no polling, no callbacks — and a single number typically answers in about a second. The dashboard, the single-number API and the synchronous multi-number API all run the same Telegram verdict against the same balance, so they agree. Each result reflects registration status at the moment of the check; run the check again whenever you need a current answer.
Permanent balance is a one-time purchase and does not renew. 30-day plan balance is valid for 30 days from payment; unused balance expires at the end of the current cycle. Plans renew automatically every 30 days until you turn off auto-renewal. Turning it off stops future charges; the current plan stays usable until it expires. Checks that fail or are undetermined are refunded to the relevant wallet.
Create a free account and contact support for 100 free checks, usable on any product; you can top up at any time.
Permanent top-ups can be paid by credit card, other supported card payments, or cryptocurrency. 30-day plans use secure hosted card checkout and renew every 30 days. Card payments carry no extra fee. Cryptocurrency may include a service fee, shown at checkout.
Create an API key in Settings, then call /api/v1/check with the X-API-Key header, an E.164 number and service_type=tg. The registration result comes back in that same JSON response; several numbers can be sent together through the synchronous multi endpoint.
No. A result reports Telegram registration status at the time of the check. You remain responsible for consent, recipient preferences, and applicable platform rules before contacting anyone.