# Twitch Username Checker (`maged120/twitch-username-checker`) Actor

Checks whether Twitch usernames are available or already taken, and returns the channel display name for taken handles.

- **URL**: https://apify.com/maged120/twitch-username-checker.md
- **Developed by:** [Maged](https://apify.com/maged120) (community)
- **Categories:** Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $8.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 web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — 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

**Twitch Username Checker** tells you instantly whether a **Twitch username is available or already taken** — in bulk, with the channel's display name for handles that are in use. Feed it a list of usernames and get back a clean, structured, export-ready table.

### What does Twitch Username Checker do?

This Actor checks the availability of usernames on [Twitch](https://www.twitch.tv). For each username you provide it returns whether the handle is **free to register** or **already claimed**, plus the channel's public **display name** and **URL** when the handle is taken. It accepts bare handles (`twitch`), `@handles`, and full channel URLs interchangeably.

Running it on the Apify platform gives you API access, scheduling, integrations (Google Sheets, Zapier, Make), proxy rotation, and run monitoring out of the box — so you can check thousands of names on autopilot.

### Why use Twitch Username Checker?

- **Brand protection** — verify your brand or streamer name is secured, or catch squatters.
- **Username hunting** — find short, clean, on-brand channel names that are still free before you launch.
- **Bulk vanity search** — test hundreds of candidate names in one run instead of typing them one by one.
- **Creator & lead research** — confirm which handles map to real channels and grab their display names.
- **Automation** — schedule recurring checks and get notified when a coveted handle frees up.

### How to use Twitch Username Checker

1. Open the Actor and go to the **Input** tab.
2. Paste your list of usernames into **Usernames to Check** (one per line). Handles, @handles, or full channel URLs all work.
3. (Optional) Enable a proxy if you're checking large volumes.
4. Click **Start**.
5. When the run finishes, open the **Output** tab or download the dataset as JSON, CSV, Excel, or HTML.

### Input

| Field | Type | Description |
|---|---|---|
| `usernames` | array | Usernames to check — bare handle, @handle, or full channel URL. **Required.** |
| `proxyConfiguration` | object | Optional proxy settings. Defaults to no proxy. |

```json
{
    "usernames": ["twitch", "pokimane", "zzq_free_handle_9182"],
    "proxyConfiguration": { "useApifyProxy": false }
}
```

### Output

Each username becomes one row in the dataset. You can download the dataset in various formats such as JSON, HTML, CSV, or Excel.

```json
[
    {
        "username": "pokimane",
        "handle": "pokimane",
        "isAvailable": false,
        "displayName": "pokimane",
        "profileUrl": "https://www.twitch.tv/pokimane",
        "error": null,
        "quota": "Unlimited."
    },
    {
        "username": "zzq_free_handle_9182",
        "handle": "zzq_free_handle_9182",
        "isAvailable": true,
        "displayName": null,
        "profileUrl": "https://www.twitch.tv/zzq_free_handle_9182",
        "error": null,
        "quota": "Unlimited."
    }
]
```

### Output data fields

| Field | Description |
|---|---|
| `username` | The exact input you provided. |
| `handle` | The normalized username that was checked. |
| `isAvailable` | `true` if the handle is free, `false` if taken, `null` if it couldn't be checked. |
| `displayName` | Public display name of the channel (only when taken). |
| `profileUrl` | Direct link to the Twitch channel. |
| `error` | Reason a check failed (e.g. invalid format), otherwise `null`. |
| `quota` | Usage/quota note for the run. |

### How much does it cost to check Twitch usernames?

Checks are lightweight — one small request per username — so runs are fast and cheap. A list of 1,000 usernames typically costs only a few cents of platform compute. Cost scales linearly with the number of usernames you check.

### Tips

- **Scale:** enable Apify Proxy if you're checking many thousands of handles in one run.
- **Automation:** use the Scheduler to re-check a shortlist of handles daily and get alerted when one becomes available.
- **Valid handles:** Twitch usernames are up to 25 characters and may contain letters, numbers, and underscores. Anything else is flagged as an invalid format. (Some legacy channels have shorter names.)

### FAQ, disclaimers, and support

**Is this legal?** The Actor only checks publicly available information about whether a username exists — the same thing you'd see by visiting a channel URL. It does not log in, collect private data, or scrape content behind authentication. You are responsible for using the data in compliance with Twitch's Terms of Service and applicable laws.

**Why is a handle marked available that I can't register?** Twitch reserves some names and enforces its own naming rules; availability here means no public channel currently exists for that handle.

**Found a bug or need a custom version?** Open an issue in the Actor's **Issues** tab. Custom and higher-volume solutions are available on request.

# Actor input Schema

## `usernames` (type: `array`):

Twitch usernames to check. You can paste a bare handle (e.g. twitch), an @handle, or a full channel URL — all are accepted.

## `proxyConfiguration` (type: `object`):

Proxy settings to avoid rate limiting. Apify Proxy or custom proxies are supported.

## Actor input object example

```json
{
  "usernames": [
    "twitch",
    "pokimane",
    "zzq_free_handle_9182"
  ],
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

## `dataset` (type: `string`):

No description

# 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 '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "usernames": [
        "twitch",
        "pokimane",
        "zzq_free_handle_9182"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("maged120/twitch-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 '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "usernames": [
        "twitch",
        "pokimane",
        "zzq_free_handle_9182",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("maged120/twitch-username-checker").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).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": [
    "twitch",
    "pokimane",
    "zzq_free_handle_9182"
  ]
}' |
apify call maged120/twitch-username-checker --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,maged120/twitch-username-checker"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/YRpeO6ccdsrrTg90N/builds/bBKrVRv1hz6HmPmhd/openapi.json