Social 2 Endpoints 5 Key Features

Telegram Username Checker API

Check username availability across supported social media platforms. 3-32 chars, start with a letter, letters, numbers, single underscores only, no trailing underscore

Category Social
Endpoints 2
Key Features 5
Frequently Asked Questions 1

Used by people at amazing companies

VercelLLM PulseOLXCasa ModernaPipeCal.comBeehiivSnykTogglRemoteSprigDeel

Trust signals before you integrate

Transparent docs, authenticated requests, and visible reliability details make it easier to evaluate DomScan before you ship.

99.99% Uptime

Production-ready endpoints are designed for 99.99% uptime and documented status handling.

OpenAPI API artifacts

OpenAPI, Swagger, Postman, CLI, SDK, and MCP links are one click away.

API keys Protected access

Authenticated endpoints use API keys with clear credit costs before you call them.

10,000 Free allowance

Start with 10,000 monthly credits and upgrade only when usage grows.

What this API helps you ship

Use this page as a production brief: endpoints, examples, response shape, and the workflow pieces needed to plug DomScan into your own product.

Product workflows

Embed domain checks, DNS intelligence, risk signals, or enrichment into onboarding, search, and internal tools.

Analyst automation

Replace repeated manual lookups with scheduled jobs, alerting, and reproducible investigation steps.

Clean JSON data

Use predictable fields, documented status codes, and credit costs instead of scraping provider pages.

AI and ops tooling

Feed agents, dashboards, SOAR playbooks, and CRMs through OpenAPI, SDK, Postman, or MCP.

Integration workflow

A simple path from first request to repeatable production usage.

1
Authenticate once

Send your API key with the documented header and keep requests consistent across services.

2
Query with examples

Start from the curl and HTTP samples, then map the parameters into your application code.

3
Operate and monitor

Use status codes, credit costs, and response fields to build retries, logs, and alerts.

Developer kit

Jump from this page into machine-readable docs, request collections, SDKs, or agent tooling.

Parameters and response map

Scan the inputs, output fields, and status codes before wiring the endpoint into your client.

Request parameters

Parameter

handleplatforms
Response fields

Example Response

handleavailabilityavailability.telegramavailability.telegram.availableavailability.telegram.profile_urlavailability.telegram.checkedavailability.telegram.requestedavailability.telegram.methodavailability.telegram.confidenceavailability.telegram.latency_msavailability.telegram.evidencesummary
Status coverage

HTTP Status Codes

200400401402429500502503504

Endpoints

GET /v1/social
Credits: 2Authentication: Authentication required
handleplatforms
GET /v1/social/info
Credits: 0Authentication: optional

Social Handle Availability

Telegram

telegram, tg

3-32 chars, start with a letter, letters, numbers, single underscores only, no trailing underscore

GET /v1/social?handle=mybrand&platforms=telegram https://t.me/mybrand status=live method=public_profile confidence=medium

APIs

26 Endpoints

Check username availability across supported social media platforms.

GET /v1/social?handle=mybrand GET /v1/social/info

Authentication

Credits

Include your API key in requests using the Authorization header:

X-API-Key: YOUR_API_KEY Authorization: Bearer YOUR_API_KEY

GitHub

github

1-39 chars, alphanumeric and hyphens, cannot start/end with hyphen

GET /v1/social?handle=mybrand&platforms=github

GitLab

gitlab

1-255 chars, letters, numbers, underscores, hyphens, and periods; cannot start with hyphen or end with period, .git, or .atom

GET /v1/social?handle=mybrand&platforms=gitlab

Bitbucket

bitbucket, bb

1-255 chars, letters, numbers, underscores, and hyphens

GET /v1/social?handle=mybrand&platforms=bitbucket

Dev.to

devto, dev.to

2-30 chars, letters, numbers, underscores, and hyphens

GET /v1/social?handle=mybrand&platforms=devto

Hugging Face

huggingface, hf

1-39 chars, alphanumeric and hyphens, cannot start/end with hyphen

GET /v1/social?handle=mybrand&platforms=huggingface

Dribbble

dribbble

1-40 chars, letters, numbers, underscores, and hyphens

GET /v1/social?handle=mybrand&platforms=dribbble

SoundCloud

soundcloud

1-40 chars, letters, numbers, underscores, and hyphens

GET /v1/social?handle=mybrand&platforms=soundcloud

Gumroad

gumroad

1-63 chars, letters, numbers, and hyphens; cannot start or end with a hyphen

GET /v1/social?handle=mybrand&platforms=gumroad

Buy Me a Coffee

buymeacoffee, bmc

1-40 chars, letters and numbers only

GET /v1/social?handle=mybrand&platforms=buymeacoffee

Substack

substack

1-63 chars, letters and numbers only

GET /v1/social?handle=mybrand&platforms=substack

itch.io

itchio, itch.io

1-30 chars, letters, numbers, underscores, and hyphens

GET /v1/social?handle=mybrand&platforms=itchio

Hacker News

hackernews, hn

1-20 chars, letters, numbers, underscores, and hyphens

GET /v1/social?handle=mybrand&platforms=hackernews

Reddit

reddit

3-20 chars, alphanumeric, underscores, and hyphens

GET /v1/social?handle=mybrand&platforms=reddit

Bluesky

bluesky, bsky

3-253 chars, domain-style handle with letters, numbers, hyphens, and periods

GET /v1/social?handle=mybrand&platforms=bluesky

X / Twitter

x, twitter

1-15 chars, alphanumeric and underscores

GET /v1/social?handle=mybrand&platforms=twitter

Instagram

instagram, ig

1-30 chars, alphanumeric, underscores, and periods

GET /v1/social?handle=mybrand&platforms=instagram

Facebook

facebook, fb

4-50 chars, alphanumeric and periods

GET /v1/social?handle=mybrand&platforms=facebook

Threads

threads

1-30 chars, alphanumeric, underscores, and periods

GET /v1/social?handle=mybrand&platforms=threads

Pinterest

pinterest

2-30 chars, alphanumeric, underscores, and periods

GET /v1/social?handle=mybrand&platforms=pinterest

Snapchat

snapchat, snap

3-15 chars, start with a letter, letters, numbers, hyphens, underscores, and periods, end with a letter or number

GET /v1/social?handle=mybrand&platforms=snapchat

Twitch

twitch

3-25 chars, alphanumeric and underscores

GET /v1/social?handle=mybrand&platforms=twitch

Patreon

patreon

1-100 chars, letters, numbers, underscores, and hyphens

GET /v1/social?handle=mybrand&platforms=patreon

TikTok

tiktok

2-24 chars, alphanumeric, underscores, and periods

GET /v1/social?handle=mybrand&platforms=tiktok

YouTube

youtube, yt

3-30 chars, alphanumeric, underscores, periods, and hyphens

GET /v1/social?handle=mybrand&platforms=youtube

LinkedIn

linkedin

3-100 chars, alphanumeric and hyphens

GET /v1/social?handle=mybrand&platforms=linkedin

Trust signals before you integrate

Transparent docs, authenticated requests, and visible reliability details make it easier to evaluate DomScan before you ship.

Uptime API artifacts

OpenAPI, Swagger, Postman, CLI, SDK, and MCP links are one click away.

API keys Protected access

Authenticated endpoints use API keys with clear credit costs before you call them.

Free allowance Sign Up for Free

Start with 10,000 monthly credits and upgrade only when usage grows.

Active Example Request

Start from the curl and HTTP samples, then map the parameters into your application code.

Key Features

Instant Results

Get availability status across all platforms in seconds.

Profile Links

Direct links to existing profiles for taken handles.

Summary Stats

Quick overview of available vs. taken platforms.

API Access

Integrate into your brand research workflow.

Combine with Domains

Check social handles alongside domain availability.

Example Request

GET /v1/social bash
curl -H "X-API-Key: $DOMSCAN_API_KEY" "https://domscan.net/v1/social?handle=mybrand&platforms=telegram"

Example Response

200 OK json
{
  "handle": "mybrand",
  "availability": {
    "telegram": {
      "available": false,
      "profile_url": "https://t.me/mybrand",
      "checked": true,
      "requested": true,
      "method": "public_profile",
      "confidence": "medium",
      "latency_ms": 104,
      "evidence": { "source": "upstream" }
    }
  },
  "summary": {
    "available_count": 0,
    "unavailable_count": 1,
    "unknown_count": 0
  },
  "summary_v2": {
    "requested_count": 1,
    "checked_count": 1,
    "available_count": 0,
    "unavailable_count": 1,
    "unknown_count": 0,
    "not_supported_count": 0,
    "determinacy_rate": 1
  }
}

Frequently Asked Questions

Why should I check social handle availability?

Brand consistency matters. If your company is called "acme", ideally you want acme.com, @acme on social platforms, and /acme on GitHub. Checking early helps you pivot if needed.

Related Tools & Resources

HTTP Status Codes

We document the HTTP status codes you should handle so you can distinguish successful responses, auth issues, credits, rate limits, missing data, and upstream failures.

OK 200

Request successful

Bad Request 400

Invalid parameters

Unauthorized 401

Missing or invalid API key/session.

Payment Required 402

Not enough credits to run this request.

Too Many Requests 429

Rate limit exceeded

Server Error 500

Internal error

Bad Gateway 502

Upstream RDAP error

Service Unavailable 503

Upstream service unavailable or temporarily rate limited.

Gateway Timeout 504

Upstream lookup timed out.

Start for free with 10,000 credits per month. Start checking domains in seconds.