Bulk product tg_batch
Telegram registration check · Bulk
Upload a whole file of numbers, find out which ones are registered on Telegram, and download the result file when it finishes.
API contract
Two calls run a whole task
Submit to get a task id, then check the task by that id. When it succeeds the response carries the result file download link — there is no third endpoint.
curl -X POST "https://tgvalidator.com/api/v1/bulk-tasks" \
-H "X-API-Key: sk_your_api_key" \
-F service_type=tg_batch \
-F file=@numbers.txtcurl "https://tgvalidator.com/api/v1/bulk-tasks/123" -H "X-API-Key: sk_your_api_key"{
"code": 0,
"msg": "ok",
"data": {
"id": 123,
"product": "tg_batch",
"status": "success",
"total": 2000,
"success_cnt": 2000,
"charged_amount_micros": 4000000,
"result_url": "https://…/result.zip"
}
}Result fields
Columns in the result file
The download is a zip: alongside this full table it splits registered and unregistered numbers into separate lists.
| Column | Example | Meaning |
|---|---|---|
number | +14155552671 | The submitted phone number, exactly as it appeared in your file. |
activated | yes | Whether the number is registered on Telegram. |
How it runs
What happens to a bulk task
Bulk is not realtime made bigger — it is submit once, run in the background, collect later. You do not need to keep the page open; task state and results stay in your dashboard.
- Upload the fileA .txt or .csv with one number per line. It is streamed straight through; nothing is written to disk.
- Precheck and reserveFormat and single-country rules are checked first, then balance is reserved for the valid lines. Nothing is charged if the precheck fails.
- Run in the backgroundThe task runs on its own — close the page if you like. A failure is reported straight away and fully refunded.
- Download the resultCollect the file from the bulk check page. You pay only for numbers that actually returned a result; the difference is refunded.
Best for
When to reach for this one
- Scheduled list hygiene
- Pre-campaign filtering
- CRM data cleanup
- Verifying purchased lists
Telegram bulk registration check is built for lists of thousands to a million numbers: upload a file of E.164 numbers, the task runs in the background, and you download a result file when it completes. It suits list hygiene, pre-campaign filtering, and cleaning up stored data — cases where you do not need an answer this second, you need a whole file done.
Clear boundaries
What this product does not do
- It is not identity verification. A result describes the number's public state on the platform; it cannot confirm who owns the number.
- It never returns message history, conversation content, or any private account content.
- Choose the country your numbers belong to when submitting a task. The list should be essentially that one country — neighbours on the same dialling code do not count as cross-country, and more than 10% genuinely from other countries is rejected before any charge.
- Results reflect the moment the task ran. Run it again for a fresh state — stored results are never refreshed for you.
- Download links expire. Fetch the file soon after the task finishes; if a link expires, check the task again for a new one.
Product FAQ
About Registration check
Why is the minimum 2,000 numbers?
Below that, the realtime endpoints are cheaper and faster — one request returns the whole answer with no task scheduling. Bulk earns its keep on whole large lists.
What happens to invalid numbers in the file?
The precheck drops malformed lines and they never enter the billable count. Of the numbers that remain, any the upstream cannot resolve are not charged either — you pay only for numbers that actually return a result.
How long does a task take?
It depends on the number count and the product. You can close the page after submitting; the task runs in the background and the result waits for you on the bulk check page.
Do I get refunded if it fails?
Yes. A failed task is refunded in full. If the task succeeds but some numbers return nothing, that portion is refunded automatically. The gap between what was reserved and what was actually charged always comes back.
Choosing
Realtime check or bulk check
| Realtime check | Bulk check | |
|---|---|---|
| How many numbers | 1 for a single check; up to 500 in the dashboard, up to 100 via the multi endpoint | From 2,000 up to 1,000,000 |
| Getting results | Right away: single and multi-endpoint answer in the same response; the dashboard returns them one by one | Download a result file when the task finishes |
| Country / region | No restriction — mix freely in one request | Pick one country/region on submission; the list should be essentially that country, and too many numbers from elsewhere are rejected before any charge |
| Result shape | JSON, fields per number | Result file (zip with the full table and split lists) |
| Typical use | Form validation, agent lookups, pre-send gating | List hygiene, pre-campaign filtering, stored-data cleanup |
Related products
Other bulk products
tg_active_batchTelegram activity check · BulkRegistration status plus username, user ID, last-seen time, active days and the member flag across a whole list.tg_profile_batchTelegram profile check · BulkUsername, user ID, first and last name, gender, age band, ethnicity and avatar across a whole list, plus last-seen time, active days and the member flag — a superset of the activity check.Create an account to submit a bulk task
Bulk and realtime checks draw on the same balance — nothing extra to enable. Sign up and upload your first file on the bulk check page.