POST /api/v1/bulk-taskscurl -X POST "https://tgvalidator.com/api/v1/bulk-tasks" \
-H "X-API-Key: sk_your_api_key" \
-F service_type=tg_username_batch \
-F file=@usernames.txtPOST /api/v1/bulk-tasksservice_type=tg_username_batchBulk product tg_username_batch
Upload a list of Telegram usernames, confirm which ones belong to real accounts, and get the avatar URL.
An add-on for whole large lists — for a handful of numbers the realtime check answers in the same request. Realtime check →
/api/v1/bulk-tasksAPI contract
Submitting returns a task id right away; check the task by that id and, once it succeeds, the response carries the result file download link. Each request is shown with its own response.
Balance for the valid lines is reserved, to be settled on completion, and the task starts running in the background.
POST /api/v1/bulk-taskscurl -X POST "https://tgvalidator.com/api/v1/bulk-tasks" \
-H "X-API-Key: sk_your_api_key" \
-F service_type=tg_username_batch \
-F file=@usernames.txt200 OK{
"code": 0,
"msg": "ok",
"data": {
"id": "3f9c2a7d8e4b4c1a9f0e6b2d5c8a7e13",
"product": "tg_username_batch",
"status": "processing",
"total": 2000,
"created_at": "2026-09-08T09:30:00Z"
}
}Poll by task id. A successful response carries the success and failure counts and the result file download link.
GET /api/v1/bulk-tasks/{id}curl "https://tgvalidator.com/api/v1/bulk-tasks/3f9c2a7d8e4b4c1a9f0e6b2d5c8a7e13" \
-H "X-API-Key: sk_your_api_key"200 OK{
"code": 0,
"msg": "ok",
"data": {
"id": "3f9c2a7d8e4b4c1a9f0e6b2d5c8a7e13",
"product": "tg_username_batch",
"status": "success",
"total": 2000,
"success_cnt": 1980,
"failure_cnt": 20,
"result_url": "https://…/result.zip",
"created_at": "2026-09-08T09:30:00Z"
}
}How it runs
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.
A .txt or .csv with one number per line. It is streamed straight through; nothing is written to disk.
Format and single-country rules are checked first, then balance is reserved for the valid lines and settled on completion. Nothing is charged if the precheck fails.
The task runs on its own — close the page if you like. A failure is reported straight away and fully refunded.
Collect the file from the bulk check page. You pay only for numbers that actually returned a result; the difference is refunded.
Result fields
The download is a zip: alongside this full table it splits registered and unregistered numbers into separate lists.
username · alex_kim — The submitted username (without @).activated · yes — Whether the username belongs to an existing Telegram account.avatar_url · <image url> — Public avatar URL, empty when the account has none.Best for
Direct answer
Telegram bulk username check takes @usernames instead of phone numbers: it confirms whether each username belongs to an existing Telegram account and returns the public avatar URL. No country to choose; one username per line, with or without the @ or t.me/ prefix.
Clear boundaries
When bulk fits
| Realtime check | Bulk check | |
|---|---|---|
| How many numbers | 1 number per single check; several per multi request — exact caps are in the API docs | A whole large list in one task — the current size range is on the pricing page |
| 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 |
Product FAQ
Use bulk for a whole large list. For a handful of numbers the realtime check answers in the same request, with no task to schedule.
The precheck drops malformed lines, so 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.
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.
Yes. A failed task is refunded in full. If the task succeeds but some numbers return nothing, that portion is refunded automatically. The difference between the reserved amount and what was actually charged always comes back.
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.