How TG Validator verifies a Telegram number
TG Validator returns a Telegram registration result for service_type=tg, synchronously for single and multi checks. This page covers the check flow, the registered field, and the limits of the result.
Reviewed August 31, 2026
What happens during a Telegram check?
TG Validator checks one number at a time and returns the result in the same HTTP response. registered=true indicates a registered number; registered=false can mean unregistered or banned. banned=true confirms a ban, false confirms no ban, and null means the ban status is unknown. Failed or undetermined checks return an error and are refunded.
Complete one check
This section covers realtime checks: the SaaS dashboard and the synchronous REST endpoints share one check service and one response meaning. Very large lists have an asynchronous bulk option, covered at the end of this page.
- 1
Submit a number
Submit one E.164 number with its country code, as described in the API documentation.
- 2
Use service_type=tg
The tg product checks whether the number was registered on Telegram at check time.
- 3
Read the result
Read registered in the same response. Run a new check when you need an updated status.
Which number format to submit
TG Validator accepts one number per check, written in E.164 format: a plus sign, the country code, then the subscriber number with no spaces or punctuation — for example +12345678900. This is the same format the Telegram app stores internally, so a number in this form maps to exactly one account. A number without a country code cannot be checked reliably: the same digits exist in many countries.
- Always include the country code; do not rely on the country of your own account.
- Strip spaces, dashes, brackets and leading zeros used for national dialling — keep only + and digits.
- Numbers in the wrong format are rejected before any charge; a rejected format is not a "not registered" result.
What does registered mean?
Read registered and banned together. registered is a boolean registration signal; false can mean unregistered or banned. banned=true confirms a Telegram ban, banned=false confirms no ban, and banned=null means a cached or historical result has no recorded ban status. Missing or null ban status must not be treated as confirmed unbanned. Invalid numbers, timeouts and undetermined checks return an error and are refunded. Refresh an old result before making a decision.
- registered=true means registered.
- registered=false can mean unregistered or banned; read banned to distinguish them.
- Handle other outcomes according to the API response code; do not infer registered yourself.
Use the result within its scope
A check reflects the status at request time. It is not identity verification or permission to contact someone.
- It does not confirm who owns the number, whether they are online at this moment, or any message content; the activity products return active days (days since last seen), not live presence.
- A registered result does not establish consent to contact the number.
- Run a new check when the business decision needs a current status.
Very large lists: the asynchronous option
The dashboard multi check and the API multi endpoint cover most lists. Only when a list far exceeds those limits does it make sense to submit the whole file as one asynchronous bulk task — you choose the country the list belongs to, and it should be essentially that one country.
- Upload a .txt or .csv with one E.164 number per line, from the bulk check page or through the API.
- Choose the country the numbers belong to when submitting; the list should be essentially that one country. Too many numbers from elsewhere make the task fail while the file is being prepared — it is not sent for checking and is refunded in full.
- Balance is reserved for the valid lines on submit, you are charged only for numbers that return a result, and the difference is refunded.
- The task runs in the background; download the result file when it finishes. A failed task is refunded in full.