# Telegram Username Checker — Availability & Price Lookup (`maged120/telegram-username-checker`) Actor Check Telegram usernames in bulk: find out which are available, taken, on auction, for sale, or already sold — with the price and auction end time. Ideal for username hunting, brand protection, and collectible research. API-ready. - **URL**: https://apify.com/maged120/telegram-username-checker.md - **Developed by:** [Maged](https://apify.com/maged120) (community) - **Categories:** Social media, Automation, Other - **Stats:** 4 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing from $10.00 / 1,000 results This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events. Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have. Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event ## What's an Apify Actor? Actors are a software tools running on the Apify platform, for all kinds of web data extraction and automation use cases. In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours, and optionally produces a well-defined JSON output, datasets with results, or files in key-value store. In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server. Actors are written with capital "A". ## How to integrate an Actor? If asked about integration, you help developers integrate Actors into their projects. You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready. The best way to integrate Actors is as follows. In JavaScript/TypeScript projects, use official [JavaScript/TypeScript client](https://docs.apify.com/api/client/js.md): ```bash npm install apify-client ``` In Python projects, use official [Python client library](https://docs.apify.com/api/client/python.md): ```bash pip install apify-client ``` In shell scripts, use [Apify CLI](https://docs.apify.com/cli/docs.md): ````bash # MacOS / Linux curl -fsSL https://apify.com/install-cli.sh | bash # Windows irm https://apify.com/install-cli.ps1 | iex ```bash In AI frameworks, you might use the [Apify MCP server](https://docs.apify.com/platform/integrations/mcp.md). If your project is in a different language, use the [REST API](https://docs.apify.com/api/v2.md). For usage examples, see the [API](#api) section below. For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt). # README ### What does Telegram Username Checker do? **Telegram Username Checker** tells you the exact status of any Telegram username in bulk. For every username you submit, it reports whether the handle is **available**, **taken**, **on auction**, **for sale**, or already **sold** — and when a username is on the marketplace, it also returns the **price in TON, the approximate price in USD, and the auction end time**. Paste a list of usernames, press **Start**, and get a clean, structured result for each one. Run it on the [Apify platform](https://apify.com) to schedule checks, call it from the API, integrate it into your own workflows, and run large lists reliably with built-in proxy rotation. ### Why use Telegram Username Checker? - **Username hunting** — find short, rare, or brandable handles that are still free to register. - **Buying & investing** — spot usernames that are on auction or for sale and see the asking price at a glance. - **Market research** — track what comparable usernames have sold for. - **Brand protection** — monitor whether handles tied to your brand are taken, listed, or sold. - **Bulk & automated** — check up to 1,000 usernames per run, on a schedule, via the API. ### How to use Telegram Username Checker 1. Open the Actor and go to the **Input** tab. 2. Enter your Telegram usernames — one per line (the leading `@` is optional). 3. Optionally choose a **Results to return** filter (all, only for sale, or only available). 4. Press **Start**. 5. When the run finishes, open the **Output** tab or download the dataset. That's it — no accounts, no setup. ### Input | Field | Description | | --- | --- | | **Telegram usernames to check** | The list of usernames to check, one per line (up to 1,000). | | **Results to return** | Return all results, only usernames for sale/on auction, or only usernames available to register. | | **Check registration availability** | For usernames not on the marketplace, also report whether they are free to register or already taken. | | **Proxy configuration** | Proxy used for the lookups. The default (Apify residential proxy) is recommended for large lists. | #### Input example ```json { "usernames": ["durov", "king", "crypto", "dmw_king"], "resultsFilter": "all", "checkAvailability": true, "proxyConfiguration": { "useApifyProxy": true, "apifyProxyGroups": ["RESIDENTIAL"] } } ```` ### Output Each username produces one record. You can download the dataset in various formats such as JSON, HTML, CSV, or Excel. #### Output example ```json [ { "username": "dmw_king", "status": "on_auction", "for_sale": true, "price_ton": 10, "price_usd": 15.47, "auction_ends_at": "2026-07-02T10:34:41+00:00", "url": "https://fragment.com/username/dmw_king" }, { "username": "king", "status": "sold", "for_sale": false, "price_ton": 675000, "price_usd": null, "auction_ends_at": null, "url": "https://fragment.com/username/king" }, { "username": "somerandomhandle", "status": "available", "for_sale": false, "price_ton": null, "price_usd": null, "auction_ends_at": null, "url": null } ] ``` #### Data fields | Field | Description | | --- | --- | | `username` | The username that was checked. | | `status` | One of `available`, `taken`, `on_auction`, `for_sale`, or `sold`. | | `for_sale` | `true` when the username can be bought right now (on auction or for sale). | | `price_ton` | Price / minimum bid in TON, when applicable. | | `price_usd` | Approximate price in USD, when available. | | `auction_ends_at` | Auction end time (ISO 8601), for usernames on auction. | | `url` | Link to the username's marketplace page, when it is listed. | ### How much does it cost? Checking usernames is lightweight, so runs are inexpensive. A typical list of a few hundred usernames costs only a fraction of a compute unit. You can start on the **Apify free tier** and only pay for what you use. Use the **Results to return** filter to keep only the records you care about. ### Tips - For the fastest, most reliable runs on large lists, keep the **Apify residential proxy** enabled. - Turn off **Check registration availability** if you only care about marketplace status (for sale / sold) — runs finish faster. - Schedule the Actor to re-check a watchlist of usernames and get notified when one becomes available or goes on sale. ### FAQ and support **Is this legal?** The Actor only reads publicly available information about username status and pricing. It does not access private data or require you to log in. **Why is a username "available" but also shows as sold?** A username can be sold on the marketplace but not yet assigned to a profile — the status field always reports the single most relevant state. **Found an issue or need a custom version?** Open the **Issues** tab on the Actor's page — feedback and custom requests are welcome. # Actor input Schema ## `usernames` (type: `array`): List of Telegram usernames to check (up to 1000 per run). Enter one username per line, with or without the leading @. ## `proxyConfiguration` (type: `object`): Proxy settings used for the lookups. Keeping the default (Apify residential proxy) gives the most reliable results on large lists. ## Actor input object example ```json { "usernames": [ "durov", "king", "crypto", "dmw_king" ], "proxyConfiguration": { "useApifyProxy": true, "apifyProxyGroups": [ "RESIDENTIAL" ] } } ``` # Actor output Schema ## `results` (type: `string`): Dataset containing one record per checked username. # API You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup. ## JavaScript example ```javascript import { ApifyClient } from 'apify-client'; // Initialize the ApifyClient with your Apify API token // Replace the '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = { "usernames": [ "durov", "king", "crypto", "dmw_king" ] }; // Run the Actor and wait for it to finish const run = await client.actor("maged120/telegram-username-checker").call(input); // Fetch and print Actor results from the run's dataset (if any) console.log('Results from dataset'); console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`); const { items } = await client.dataset(run.defaultDatasetId).listItems(); items.forEach((item) => { console.dir(item); }); // 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs ``` ## Python example ```python from apify_client import ApifyClient # Initialize the ApifyClient with your Apify API token # Replace '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = { "usernames": [ "durov", "king", "crypto", "dmw_king", ] } # Run the Actor and wait for it to finish run = client.actor("maged120/telegram-username-checker").call(run_input=run_input) # Fetch and print Actor results from the run's dataset (if there are any) print("💾 Check your data here: https://console.apify.com/storage/datasets/" + run["defaultDatasetId"]) for item in client.dataset(run["defaultDatasetId"]).iterate_items(): print(item) # 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start ``` ## CLI example ```bash echo '{ "usernames": [ "durov", "king", "crypto", "dmw_king" ] }' | apify call maged120/telegram-username-checker --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "command": "npx", "args": [ "mcp-remote", "https://mcp.apify.com/?tools=maged120/telegram-username-checker", "--header", "Authorization: Bearer " ] } } } ``` ## OpenAPI specification ```json { "openapi": "3.0.1", "info": { "title": "Telegram Username Checker — Availability & Price Lookup", "description": "Check Telegram usernames in bulk: find out which are available, taken, on auction, for sale, or already sold — with the price and auction end time. Ideal for username hunting, brand protection, and collectible research. API-ready.", "version": "0.1", "x-build-id": "Q963GGazfo8tXqtzS" }, "servers": [ { "url": "https://api.apify.com/v2" } ], "paths": { "/acts/maged120~telegram-username-checker/run-sync-get-dataset-items": { "post": { "operationId": "run-sync-get-dataset-items-maged120-telegram-username-checker", "x-openai-isConsequential": false, "summary": "Executes an Actor, waits for its completion, and returns Actor's dataset items in response.", "tags": [ "Run Actor" ], "requestBody": { "required": true, "content": { "application/json": { "schema": { "$ref": "#/components/schemas/inputSchema" } } } }, "parameters": [ { "name": "token", "in": "query", "required": true, "schema": { "type": "string" }, "description": "Enter your Apify token here" } ], "responses": { "200": { "description": "OK" } } } }, "/acts/maged120~telegram-username-checker/runs": { "post": { "operationId": "runs-sync-maged120-telegram-username-checker", "x-openai-isConsequential": false, "summary": "Executes an Actor and returns information about the initiated run in response.", "tags": [ "Run Actor" ], "requestBody": { "required": true, "content": { "application/json": { "schema": { "$ref": "#/components/schemas/inputSchema" } } } }, "parameters": [ { "name": "token", "in": "query", "required": true, "schema": { "type": "string" }, "description": "Enter your Apify token here" } ], "responses": { "200": { "description": "OK", "content": { "application/json": { "schema": { "$ref": "#/components/schemas/runsResponseSchema" } } } } } } }, "/acts/maged120~telegram-username-checker/run-sync": { "post": { "operationId": "run-sync-maged120-telegram-username-checker", "x-openai-isConsequential": false, "summary": "Executes an Actor, waits for completion, and returns the OUTPUT from Key-value store in response.", "tags": [ "Run Actor" ], "requestBody": { "required": true, "content": { "application/json": { "schema": { "$ref": "#/components/schemas/inputSchema" } } } }, "parameters": [ { "name": "token", "in": "query", "required": true, "schema": { "type": "string" }, "description": "Enter your Apify token here" } ], "responses": { "200": { "description": "OK" } } } } }, "components": { "schemas": { "inputSchema": { "type": "object", "required": [ "usernames" ], "properties": { "usernames": { "title": "Telegram usernames to check", "maxItems": 1000, "type": "array", "description": "List of Telegram usernames to check (up to 1000 per run). Enter one username per line, with or without the leading @.", "items": { "type": "string" } }, "proxyConfiguration": { "title": "Proxy configuration", "type": "object", "description": "Proxy settings used for the lookups. Keeping the default (Apify residential proxy) gives the most reliable results on large lists.", "default": { "useApifyProxy": true, "apifyProxyGroups": [ "RESIDENTIAL" ] } } } }, "runsResponseSchema": { "type": "object", "properties": { "data": { "type": "object", "properties": { "id": { "type": "string" }, "actId": { "type": "string" }, "userId": { "type": "string" }, "startedAt": { "type": "string", "format": "date-time", "example": "2025-01-08T00:00:00.000Z" }, "finishedAt": { "type": "string", "format": "date-time", "example": "2025-01-08T00:00:00.000Z" }, "status": { "type": "string", "example": "READY" }, "meta": { "type": "object", "properties": { "origin": { "type": "string", "example": "API" }, "userAgent": { "type": "string" } } }, "stats": { "type": "object", "properties": { "inputBodyLen": { "type": "integer", "example": 2000 }, "rebootCount": { "type": "integer", "example": 0 }, "restartCount": { "type": "integer", "example": 0 }, "resurrectCount": { "type": "integer", "example": 0 }, "computeUnits": { "type": "integer", "example": 0 } } }, "options": { "type": "object", "properties": { "build": { "type": "string", "example": "latest" }, "timeoutSecs": { "type": "integer", "example": 300 }, "memoryMbytes": { "type": "integer", "example": 1024 }, "diskMbytes": { "type": "integer", "example": 2048 } } }, "buildId": { "type": "string" }, "defaultKeyValueStoreId": { "type": "string" }, "defaultDatasetId": { "type": "string" }, "defaultRequestQueueId": { "type": "string" }, "buildNumber": { "type": "string", "example": "1.0.0" }, "containerUrl": { "type": "string" }, "usage": { "type": "object", "properties": { "ACTOR_COMPUTE_UNITS": { "type": "integer", "example": 0 }, "DATASET_READS": { "type": "integer", "example": 0 }, "DATASET_WRITES": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_READS": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_WRITES": { "type": "integer", "example": 1 }, "KEY_VALUE_STORE_LISTS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_READS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_WRITES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_INTERNAL_GBYTES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_EXTERNAL_GBYTES": { "type": "integer", "example": 0 }, "PROXY_RESIDENTIAL_TRANSFER_GBYTES": { "type": "integer", "example": 0 }, "PROXY_SERPS": { "type": "integer", "example": 0 } } }, "usageTotalUsd": { "type": "number", "example": 0.00005 }, "usageUsd": { "type": "object", "properties": { "ACTOR_COMPUTE_UNITS": { "type": "integer", "example": 0 }, "DATASET_READS": { "type": "integer", "example": 0 }, "DATASET_WRITES": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_READS": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_WRITES": { "type": "number", "example": 0.00005 }, "KEY_VALUE_STORE_LISTS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_READS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_WRITES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_INTERNAL_GBYTES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_EXTERNAL_GBYTES": { "type": "integer", "example": 0 }, "PROXY_RESIDENTIAL_TRANSFER_GBYTES": { "type": "integer", "example": 0 }, "PROXY_SERPS": { "type": "integer", "example": 0 } } } } } } } } } } ```