# All In One Username Availability Checker (`scraperoka/all-in-one-username-availability-checker`) Actor 🔍 Check username availability in seconds! Find matching handles across platforms instantly with All In One Username Availability Checker. 🚀 Perfect for brands, creators & developers—save time and secure your name fast! ✨ - **URL**: https://apify.com/scraperoka/all-in-one-username-availability-checker.md - **Developed by:** [Scraperoka](https://apify.com/scraperoka) (community) - **Categories:** Social media, Lead generation, Developer tools - **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing from $2.99 / 1,000 results This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage. 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 ### All-In-One Username Availability Checker 🎯 Manually visiting dozens of profiles to find out whether a handle is free wastes hours you don’t have. **All-In-One Username Availability Checker** instantly checks username availability across many platforms using your keyword and built-in reliability features. Use this **username availability checker** for marketers, recruiters, and growth teams to find instant username availability and identify the best handle in minutes—perfect for bulk username availability checker workflows that can produce thousands of results in a single run. --- ### What You Get: Sample Output Here’s a sample record from a single run: ```json [ { "id": "483920104657", "platform": "x", "profile_url": "", "status": "Available" }, { "id": "905317662184", "platform": "instagram", "profile_url": "", "status": "Unknown" }, { "id": "120048579330", "platform": "github", "profile_url": "https://github.com/emilywritespoem", "status": "Not Available" } ] ```` | Field | Type | What It Tells You | |---|---|---| | `id` | string | A unique ID for each checked platform result | | `platform` | string | The platform whose username was checked (for example, X or Instagram) | | `profile_url` | string | A direct profile link when the username is reported as **Not Available** and the actor can build the URL | | `status` | string | The availability result as one of: `Available`, `Not Available`, or `Unknown` | | `keyword` | (not included in dataset output) | Use your input keyword to interpret results across platforms | | `error_message` | (not included in dataset output) | Errors are handled internally; dataset results focus on `status` per platform | | `found` | (not included in dataset output) | The dataset exposes the final `status`, not the raw `found` flag | | `timestamp` | (not included in dataset output) | Record timing is not included in the dataset fields shown by this actor | | `request_type` | (not included in dataset output) | This actor returns only the availability status per platform | | `success` | (not included in dataset output) | You get per-platform `status` entries in the dataset output | Export your dataset as JSON, CSV, or Excel — straight from the Apify dashboard. *** ### Why All-In-One Username Availability Checker? There are a lot of ways to pull data with a username checker for websites — here’s what sets **All-In-One Username Availability Checker** apart. #### One keyword → many platforms Feed in a single username and use the **platform** selector to check **All** platforms or narrow to a specific site (like Instagram, TikTok, or X). This makes it a practical social media username availability checker for handle availability checker workflows. #### Availability statuses that are easy to act on You’ll get a clear per-platform `status` of `Available`, `Not Available`, or `Unknown`. For example, the actor sets `Unknown` for `instagram` and `twitch`, so you can quickly spot where the result needs manual follow-up. #### Clean, structured dataset output Each result item is written into the Apify dataset with consistent fields: `id`, `platform`, `profile_url`, and `status`. This makes it straightforward to plug into downstream research, lists, and automation pipelines as a custom username availability checker output. #### Built-in proxy support for reliable scraping The actor includes fallback logic that can request through different proxy approaches when direct requests fail, helping keep bulk checks running smoothly. *** ### Configuring Your Run Drop this into your `input.json` to get started: ```json { "keyword": "emilywritespoem", "platform": "All", "proxyConfiguration": { "useApifyProxy": true } } ``` | Parameter | Required | What It Does | |---|---|---| | `keyword` | ✅ | The username to search for (for example, the handle you want to claim). | | `platform` | ⬜ | Select a platform to check. Choose `"All"` to check every platform in the actor’s supported set. | | `proxyConfiguration` | ⬜ | Configure proxies for this Actor run. | *** ### Core Capabilities #### Multi-platform handle availability checks This **username availability checker** checks the availability of your handle across many supported platforms in one go. It’s designed for quick “check username availability” workflows without hopping between sites manually. #### Flexible platform targeting Choose `"All"` to run a broad check, or set `platform` to focus on a specific service (such as `TikTok`, `Instagram`, `Reddit`, or `Github`). That makes this actor a domain and username availability checker you can tailor to your exact needs. #### Resilience through fallback request logic If direct requests don’t succeed, the actor uses fallback logic to keep the run moving. This is especially useful when you’re doing a bulk username availability checker run and want fewer interruptions. #### Structured output with actionable profile links When a username is reported as `Not Available`, the actor may include a `profile_url` for platforms where it can build a profile link. That helps you immediately see where the handle is already taken. #### Dataset-first automation readiness Results are pushed to the Apify dataset so you can export and analyze them immediately. You can use the output as a username search tool for research, onboarding, or campaign planning. **In short:** **All-In-One Username Availability Checker** turns a single handle into a usable availability list fast. *** ### Who Gets the Most Out of This Here’s how different teams put **All-In-One Username Availability Checker** to work: **Growth teams & community managers** — They test candidate handles for brand consistency across multiple social media usernames availability checker targets, building a shortlist of usable handles before launching. **Marketers & influencer campaign managers** — They run an all in one username availability checker pass to validate whether influencer handles are usable on key platforms, then move forward with outreach or campaign assets faster. **Recruiters & talent ops** — They use a handle availability checker workflow to find the right public-facing presence (including usernames for platforms like X, LinkedIn, or GitHub) and avoid last-minute rebrands. **Freelance researchers & brand analysts** — They rely on structured dataset output to compare availability patterns and document findings as part of a bulk username availability checker report. **Developers & automation specialists** — They integrate the actor into a pipeline via the Apify dataset to support instant username availability decisions inside internal tools, without manual browsing. *** ### Step-by-Step: How to Use It No coding needed. Here's how to run **All-In-One Username Availability Checker** from start to finish: 1. **Open the actor on Apify** — visit the actor page on the Apify console at https://console.apify.com. 2. **Enter your inputs** — set `keyword` (required) and optionally `platform` and `proxyConfiguration`. 3. **Configure proxy settings (optional)** — use `proxyConfiguration` if you need proxy support for your run. 4. **Hit Run and watch the live log** — the actor reports progress while checking platforms. 5. **View results in the dataset tab** — open the dataset to see `platform`, `status`, and `profile_url` fields per result. 6. **Export as JSON, CSV, or Excel** — download straight from the Apify dashboard for analysis or outreach workflows. The whole process takes under 5 minutes to set up. *** ### Integrations & Export Options Once your data is collected, **All-In-One Username Availability Checker** plugs directly into your existing workflow. You can download results from the Apify dataset in common formats such as JSON, CSV, or Excel for analysis, spreadsheets, and reporting. If you’re building automation, you can also connect the actor to downstream tools using Apify’s API and no-code options like Zapier/Make (where supported). You can pull results programmatically from the Apify API and trigger follow-up actions (like updating a CRM or creating a task list) after the run completes. This makes it a practical username checker for websites and social media username availability checker use cases inside automated systems. *** ### Pricing & Free Trial All-In-One Username Availability Checker runs on the Apify platform, which offers a **free tier** — no credit card required to get started. Runs are typically billed based on Apify platform compute usage (compute units / CU), so costs scale with how much checking you do. For exact pricing details and plan options, check the Apify pricing page on the platform. Start for free at [apify.com](https://apify.com) and scale when you're ready. *** ### Reliability & Performance | What We Handle | How | |---|---| | Rate-limit / request failures | Uses fallback request logic when direct attempts don’t succeed | | Proxy reliability | Supports proxy configuration via `proxyConfiguration` and includes fallback proxy approaches | | Partial platform coverage | Skips platforms that fail after all request attempts and continues the run | | Clear per-platform outcomes | Each platform result includes `status` (`Available`, `Not Available`, or `Unknown`) | | Output readiness | Writes results to the Apify dataset as structured JSON objects | **Limitations:** Some platforms can return `Unknown` for availability in the dataset (notably `instagram` and `twitch` as handled by the actor). The actor only checks publicly visible username availability and provides the resulting `status`—not guaranteed enforcement of platform rules or future availability. For enterprise-scale runs, contact us to discuss custom configurations. *** ### Frequently Asked Questions #### Is there a free plan or trial for All-In-One Username Availability Checker? Yes. Apify offers a **free tier** for trying actors before scaling up. You can use it to validate your keyword and platform selection workflow with the username availability checker output. #### Do I need to log in to use this for each platform? No login is required for the actor itself. It checks username availability and returns a dataset result; however, individual platforms’ own visibility and access rules still apply to what the actor can verify. #### How accurate is the data returned by this username availability checker? The actor reports a per-platform `status` based on publicly available signals, returning `Available`, `Not Available`, or `Unknown`. Accuracy depends on what’s available to verify at the time of the run. #### How many results can I get per run? You’ll get one dataset result per platform checked for your chosen `platform` input. If you set `platform` to `All`, you’ll receive results across the supported platform list the actor checks. #### How fresh is the data? The dataset reflects the availability status as of when the actor completes checks during your run. It’s not a live feed—run again when you need the most up-to-date instant username availability information. #### Is this legal? Does it comply with GDPR / CCPA? This actor is intended to work with **publicly available data** and outputs availability statuses. You’re responsible for complying with GDPR, CCPA, platform Terms of Service, and any applicable local regulations for how you store and use the results. #### Can I export results to Google Sheets or Excel? Yes. You can export your dataset from the Apify dashboard and use the downloaded files in tools like Excel. If you want direct spreadsheet sync, you can use Apify integrations or automation workflows that route dataset results into your tools. #### Can I run this on a schedule automatically? Yes, you can schedule runs using Apify’s scheduling options (where enabled for your account). This is helpful for ongoing bulk username availability checker monitoring. #### Can I access this via API? Yes. You can access results programmatically via the Apify API and retrieve dataset outputs for downstream systems. This makes it easy to embed the check username availability step into your automation. #### What happens if the actor hits an error? If a platform check fails after fallback attempts, that platform is skipped while the actor continues with the rest. The dataset output you get is composed of the successfully processed platform results, each with a `status`. *** ### Need Help or Have a Request? Got a question about **All-In-One Username Availability Checker** or want a new feature added? Reach out at . We’re actively maintaining this actor based on user feedback, and you can request improvements like batch CSV upload support or webhook notifications on run completion. *** ### Disclaimer & Responsible Use *All-In-One Username Availability Checker is the fastest, most reliable way to verify handle availability across platforms—start your free run today.* This actor uses **publicly available data** and does not access private accounts, login-gated content, or password-protected pages. You are responsible for following GDPR, CCPA, platform Terms of Service, and applicable local regulations when using the results. For data removal requests, contact . Use responsibly, ethically, and only for lawful purposes. # Actor input Schema ## `keyword` (type: `string`): A username to search for ## `platform` (type: `string`): Select a platform to check. Choose "All" to check every platform. ## `proxyConfiguration` (type: `object`): Configure proxies for this Actor. ## Actor input object example ```json { "keyword": "emilywritespoem", "platform": "All" } ``` # 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 = { "keyword": "emilywritespoem" }; // Run the Actor and wait for it to finish const run = await client.actor("scraperoka/all-in-one-username-availability-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 = { "keyword": "emilywritespoem" } # Run the Actor and wait for it to finish run = client.actor("scraperoka/all-in-one-username-availability-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 '{ "keyword": "emilywritespoem" }' | apify call scraperoka/all-in-one-username-availability-checker --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "command": "npx", "args": [ "mcp-remote", "https://mcp.apify.com/?tools=scraperoka/all-in-one-username-availability-checker", "--header", "Authorization: Bearer " ] } } } ``` ## OpenAPI specification ```json { "openapi": "3.0.1", "info": { "title": "All In One Username Availability Checker", "description": "🔍 Check username availability in seconds! Find matching handles across platforms instantly with All In One Username Availability Checker. 🚀 Perfect for brands, creators & developers—save time and secure your name fast! ✨", "version": "1.0", "x-build-id": "2dDLHTKif9h500QnA" }, "servers": [ { "url": "https://api.apify.com/v2" } ], "paths": { "/acts/scraperoka~all-in-one-username-availability-checker/run-sync-get-dataset-items": { "post": { "operationId": "run-sync-get-dataset-items-scraperoka-all-in-one-username-availability-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/scraperoka~all-in-one-username-availability-checker/runs": { "post": { "operationId": "runs-sync-scraperoka-all-in-one-username-availability-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/scraperoka~all-in-one-username-availability-checker/run-sync": { "post": { "operationId": "run-sync-scraperoka-all-in-one-username-availability-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": [ "keyword" ], "properties": { "keyword": { "title": "Username", "type": "string", "description": "A username to search for", "default": "emilywritespoem" }, "platform": { "title": "Platform", "enum": [ "All", "X", "Reddit", "Github", "Medium", "Twitch", "Instagram", "Myanimelist", "Anilist", "Gumroad", "Youtube", "Bluesky", "Linktree", "Kinja", "Mix", "500px", "9gag", "About.me", "Ask.fm", "Bandcamp", "Behance", "Bitbucket", "Blip.fm", "Blogspot", "Bodybuilding", "Buymeacoffee", "Buzzfeed", "Canva", "Cash.app", "Coderwall", "Colourlovers", "Dailymotion", "Deviantart", "Disqus", "Dribbble", "Ebay", "Etsy", "Facebook", "Fiverr", "Flickr", "Flipboard", "Foursquare", "Gamespot", "Goodreads", "Ifttt", "Instructables", "Intensedebate", "Gravatar", "Houzz", "Hubpages", "Kik", "LinkedIn", "Pinterest", "Snapchat", "Tumblr", "Vimeo", "SoundCloud", "Spotify", "StackOverflow", "StackExchange", "Quora", "WhatsApp", "Weibo", "Telegram", "Discord", "TikTok", "Redbubble", "Zomato", "Yelp", "Substack", "Patreon", "OnlyFans", "Vero", "Caffeine", "DLive", "Clubhouse", "Periscope", "Baidu", "Douyin", "VK", "Odnoklassniki", "WeChat", "Line", "Skype", "Zoom", "Google", "Amazon", "Yahoo" ], "type": "string", "description": "Select a platform to check. Choose \"All\" to check every platform.", "default": "All" }, "proxyConfiguration": { "title": "Proxy Configuration", "type": "object", "description": "Configure proxies for this Actor." } } }, "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 } } } } } } } } } } ```