LinkedIn Username Checker — Profile or Company

What does LinkedIn Username Checker do?

LinkedIn Username Checker tells you whether a LinkedIn profile (/in/) or company (/company/) vanity slug is available or already taken. Paste a list of slugs (or full URLs), pick one entityType per run (default user), and download clean JSON / CSV / Excel from the dataset.

Built for bulk brand / vanity research (up to 100,000 slugs per run). Large lists are auto-split into ~3,000-item child runs on Apify, with auto-heal under auth walls. Default path uses RESIDENTIAL proxy (LinkedIn often blocks datacenter IPs).

This Actor is not affiliated with LinkedIn / Microsoft. Availability is inferred from public HTML and can change if LinkedIn alters their pages.

Key features

• Bulk checks - up to 100,000 slugs per run (invalid / duplicate inputs filtered before work starts)
• One mode per run - user (profile) or company (never both in one paid call)
• Auto-sharding - runs above ~3,000 split into child runs; one parent dataset
• Auto-heal - on auth walls / proxy failures: backoff, lower concurrency, rotate sticky session once per wave
• URL-aware input - bare slug, /in/..., or /company/... URLs
• No browser - HTTP + early-abort HTML (low compute, 256 MB)
• Success-only billing - only conclusive checks charge PPE result
• Export anywhere - JSON, CSV, Excel, HTML from the Apify dataset

Why Clovys

Clovys is a nonprofit organization driven by a single mission: to make the internet safer, faster, more reliable, and universally accessible.

We believe that data should not be locked behind exorbitant paywalls or complex technical barriers. By building lightweight, highly optimized Apify Actors, we help developers, researchers, and organizations access the information they need to innovate without friction.

As a nonprofit initiative, we do not optimize for margins. Our pricing is kept as low as possible and is strictly calculated to cover the raw infrastructure costs of data extraction - such as Apify compute units and proxy bandwidth.

For LinkedIn specifically, Clovys ships a residential-ready vanity checker with sticky sessions, early-abort streaming, and auto-heal so bulk runs stay usable when LinkedIn shows auth walls.

Use cases

• Personal / founder branding - check /in/ vanity availability
• Company pages - screen /company/ slugs before launch
• Agency workflows - bulk-check client vanity ideas
• Multi-platform suites - pair with other Clovys username checkers

How to use

1. Open LinkedIn Username Checker in Apify Console
2. Paste slugs in Slugs / usernames
3. Leave entityType as user, or switch to company for a separate run
4. Keep defaults (256 MB, concurrency 2, RESIDENTIAL proxy)
5. Click Start and download the Dataset

Input

Field	Type	Default	Description
usernames	string[]	-	Vanity slugs or LinkedIn URLs (required, up to 100,000)
entityType	string	user	user (/in/) or company (/company/) - single value only
maxConcurrency	integer	2	Parallel checks (1-10). Keep low with residential proxy
maxRetries	integer	1	Retries on network / ambiguous responses
requestDelayMs	integer	300	Pause after each check (0 = off)
proxyConfiguration	object	RESIDENTIAL	Recommended on Apify - datacenter IPs often hit auth walls

Output example

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

{
 "platform": "linkedin",
 "entityType": "user",
 "username": "williamhgates",
 "available": false,
 "displayName": "Bill Gates - Chair, Gates Foundation and Founder, Breakthrough Energy",
 "profileUrl": "https://www.linkedin.com/in/williamhgates",
 "method": "linkedin_public_html",
 "checkedAt": "2026-09-26T01:00:00.000Z",
 "error": null
}

Taken and available rows are successful results. Auth-wall / failed rows keep available: null and error set - they are not billed.

Data fields

Field	Description
platform	Always linkedin
entityType	user or company
username	Normalized vanity slug
available	true = free, false = taken, null = inconclusive
displayName	Public title when taken
profileUrl	Canonical LinkedIn URL
method	Always linkedin_public_html
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 / proxy usage).

Only conclusive results are charged as result. Failed / auth-wall rows are free on the PPE event. Checking both user and company means two runs.

Recommended settings

Goal	Settings
Production / Store	256 MB, concurrency 2, RESIDENTIAL proxy, delay 300 ms
Gentler on walls	concurrency 1, delay 400-600 ms, maxRetries: 2
Huge lists	up to 100,000 slugs - auto-shard handles the rest

FAQ

How many usernames per run? Up to 100,000. Lists above ~3,000 are auto-split into child runs; invalid / duplicate inputs are dropped before sharding.

Is "taken" billed? Yes. Both available: false (taken) and available: true (free) are conclusive result events. Only error / inconclusive rows are free.

Can I check profiles and companies in one run? No. entityType is a single value. Run once for user, once for company (separate billing).

Do I need expensive proxies? Yes, recommended - use RESIDENTIAL (default). Datacenter IPs often return auth walls and inconclusive results.

What if a check fails? It is stored with error and available: null. Other slugs continue. Failed items are not billed as result. Auto-heal may slow down and rotate the sticky proxy session.

Is this official LinkedIn data? No. This Actor is independent and unaffiliated. LinkedIn can change page behavior at any time.

Support

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