Telegram Username Checker — Available or Taken

What does Telegram Username Checker do?

Telegram Username Checker tells you whether a Telegram @username is available or already taken. Users, channels, and bots share one public namespace. Paste a list of usernames (or t.me URLs), run the Actor, and download clean JSON / CSV / Excel.

Built for bulk brand and handle research — up to 100,000 usernames per run. Large lists are handled automatically so you get one dataset without babysitting the job. Lightweight by default (256 MB).

This Actor is not affiliated with Telegram.

Why use it

• Protect your brand — see if your @ is free on Telegram
• Name channels and bots safely — one shared public namespace means one check covers all
• Bulk without friction — paste a long list; get one clean dataset
• Pay for answers — only conclusive checks are billed
• Export anywhere — JSON, CSV, Excel, HTML from the Apify dataset

Use cases

• Brand protection on Telegram
• Channel / bot naming before launch
• Agency bulk checks for client proposals
• Multi-platform naming with other Clovys checkers

How to use

1. Open Telegram Username Checker in Apify Console
2. Paste usernames in Usernames
3. Keep defaults (256 MB)
4. Click Start
5. Download results from the Dataset tab

Input

Field	Type	Default	Description
usernames	string[]	-	Usernames or t.me URLs (required, up to 100,000)
entityType	string	user	Always user (shared Telegram namespace)
maxConcurrency	integer	3	Parallelism (1–10)
maxRetries	integer	2	Retries on temporary failures
requestDelayMs	integer	200	Pause between checks (0 = off)

Output example

You can download the dataset in JSON, HTML, CSV, or Excel.

{
  "platform": "telegram",
  "entityType": "user",
  "username": "telegram",
  "available": false,
  "displayName": "Telegram News",
  "profileUrl": "https://t.me/telegram",
  "checkedAt": "2026-09-26T01:00:00.000Z",
  "error": null
}

Taken and available rows are successful results. Ambiguous / failed rows keep available: null and error set — they are not billed.

Data fields

Field	Description
platform	Always telegram
entityType	Always user
username	Normalized handle
available	true = free, false = taken, null = inconclusive
displayName	Public title when taken
profileUrl	https://t.me/{username}
checkedAt	ISO timestamp
error	Error message if the check failed

Pricing

Pay-per-event pricing (platform usage is billed separately by Apify):

Event	When charged	Price
result	Each conclusive check (available true or false)	$0.004 ($4 / 1,000)
Actor Start	Once when the run starts (scaled by memory GB)	$0.001

Example: 1,000 conclusive checks ≈ $4.00 in PPE result (+ Actor Start + Apify platform usage).

Only conclusive results are charged.

Recommended settings

Goal	Settings
Production	256 MB, concurrency 3, delay 200 ms
High volume	concurrency 5–8, shorter delay
Huge lists	up to 100,000 usernames — leave defaults

FAQ

How many usernames per run? Up to 100,000. Invalid and duplicate inputs are filtered before work starts.

Is "taken" billed? Yes. Both taken and available are conclusive. Only inconclusive / error rows are free.

Are users, channels, and bots different namespaces? No. Telegram shares one public @username space — a taken channel blocks the same handle for a user.

Do I need proxies? Usually not. If you hit limits at very high volume, lower concurrency or add Apify proxy.

What if a check fails? It is stored with error and available: null. Other usernames continue. Failed items are not billed.

Is this official Telegram data? No. This Actor is independent and unaffiliated.

Support

Questions, bugs, or feature requests: use the Actor Issues tab on Apify, or contact Clovys through the Store profile.