Telegram Number Checker — Bulk Verify Accounts via Platform or API

A Telegram number checker processes phone numbers in E.164 format and returns a row-level Telegram signal. Use the basic tg task when you only need registration status. Activity and public-profile checks are separate products with different fields and costs; do not assume the basic result contains them.

You can run a batch without code in the Telegram product interface, or automate recurring lists with the REST API described below.

Choose the Telegram result depth first

Check	API task type	Core output	Best suited to
Registration	`tg`	Submitted number and registration status	Removing unregistered rows and basic list segmentation
Activity	`tg_active`	Registration plus available identifiers, last-seen time, active days, and member status	Recency-based internal segmentation
Public profile	`tg_avatar`	Registration plus available profile, avatar, activity, and image-derived attributes	Authorised profile-enrichment review

Optional profile fields can be empty. Age and gender attributes derived from a public avatar are probabilistic estimates, not verified facts, and should not be used to make consequential decisions about a person. The current Telegram product page shows the configured outputs for each tier.

Prepare the input file

Create a .txt or .csv file with one international-format phone number per row. Keep your own stable record ID in the source system so each exported row can be mapped back safely.

+14155550100
+41798284651
+447700900123

Validate country codes and remove extensions before submitting. A formatting error should be treated differently from a confirmed “not registered” result.

Submit a Telegram registration task

Official reference: Telegram Bulk CheckNumber API.

POST https://api.checknumber.ai/v1/tasks

Parameter	Description
`file`	One E.164 phone number per line
`task_type`	`tg` for the basic Telegram registration check

curl --location 'https://api.checknumber.ai/v1/tasks' \
  --header 'X-API-Key: API-KEY' \
  --form 'file=@"./numbers.txt"' \
  --form 'task_type="tg"'

Store the returned task_id. Do not expose the API key in client-side code, browser logs, analytics events, or shared screenshots.

Poll the task and download results

POST https://api.checknumber.ai/v1/gettasks

curl --location 'https://api.checknumber.ai/v1/gettasks' \
  --header 'X-API-Key: API-KEY' \
  --form 'task_id="TASK_ID"'

Poll with a sensible interval instead of sending continuous requests. When the task reaches exported, retrieve the file from result_url.

Task field	Meaning
`created_at`, `updated_at`	Creation and latest status timestamps
`task_id`	Identifier used for status requests
`status`	For example `pending`, `processing`, or `exported`
`total`	Rows submitted in the task
`success`, `failure`	Completed and failed row counts
`result_url`	Download location after export

For the basic tg task, the important result columns are the submitted Number and the telegram registration verdict. Follow the documentation for the current response keys rather than hard-coding fields from an older export.

Handle failures without corrupting the list

Response	Billing described by the API	Application behaviour
`200`	Chargeable successful request	Save the task ID or returned status
`400`	Not charged	Correct parameters or file format before retrying
`500`	Not charged	Retry later with backoff

Keep three groups in downstream processing: confirmed registered, confirmed not registered, and unresolved/error. Retrying only unresolved rows prevents a temporary failure from being mistaken for a negative Telegram result.

What Telegram registration does not prove

A registration match does not prove that the account is recently active, belongs to the expected individual, consents to contact, or will respond. Likewise, a last-seen or public-profile signal can be missing because of availability and privacy conditions.

Use the minimum result depth your workflow needs, document why the data is processed, and apply local privacy and outreach requirements. CheckNumber.AI does not need to message the submitted number to produce the described registration result.

Implementation checklist

Normalise numbers to E.164 and preserve a source record ID.
Select tg, tg_active, or tg_avatar based on required fields—not on the most fields available.
Submit one platform-specific task and save its task_id.
Poll with backoff until the task reaches a terminal state.
Download promptly and separate confirmed results from errors.
Review the official API docs and current pricing before production use.

Frequently asked questions

How long does a one-million-number task take?

Processing time varies with server load and platform rate limits. Do not design an integration around a guaranteed completion time; monitor the task status instead.

Does the check send a Telegram message?

No. The registration check does not message or notify the submitted number.

Can one task check Telegram and other platforms?

No. Each task is platform-specific. Submit separate tasks when a workflow needs results from more than one platform.

What happens if the available credit is insufficient?

Successfully processed rows consume credit. Review the returned task and row statuses rather than assuming every submitted row completed.

Telegram Number Checker — Bulk Verify Accounts via Platform or API | CheckNumber.AI