Check handle availability across Instagram, TikTok, Facebook, Pinterest, YouTube (@), and X (Twitter) in one run. Built for founders and agencies picking a brand name. Export JSON/CSV from the dataset.
Threads — new platform threads and column available_threads. Uses Instagram’s public web_profile_info endpoint (same @username as Threads for Meta accounts). On Apify Cloud, requests use the residential proxy like other Meta checks. Dependency: got-scraping (avoids undici Sec-Fetch errors on i.instagram.com).
1.5
Changed
Input (Console): Removed the Advanced (Instagram) section (instagramCookies, proxyGroups) from input_schema.json so the default UI only shows handles and platforms. The Actor still accepts those keys via the API; Instagram continues to use the RESIDENTIAL proxy group by default on Apify.
Input copy: Simpler English descriptions for the Actor form (no bulk-edit / JSON paste instructions).
1.4
Fixed
Pinterest: Availability no longer uses the profile HTML shell (profile / PinCount appear in every page’s JS). Detection uses the public /feed.rss endpoint first: HTTP 200 + RSS XML means the username exists; 404 + User not found means it is available. HTML remains a narrow fallback.
1.3
Changed
Run logs: removed emoji and Unicode banner characters; ASCII separators and plain indented lines only (aligned with perfect-apify-actor premium logging guidance).
1.2.1
Changed
Logs: Progress bar + % + step counter + ETA (aligned with facebook-ads-library-scraper), shorter plain-English lines; Actor.setStatusMessage shows % · step/total on Apify. Removed long per-network lines from the live log.
1.2.0
Removed
LinkedIn — public /in/{slug} is not aligned with a cross-network “vanity handle” check; column available_linkedin and all LinkedIn logic removed.
1.1.2
Fixed
X (Twitter): Availability via oEmbed (publish.twitter.com) instead of x.com HTML; minimal curl-style User-Agent avoids Cloudflare 403 on server-side fetch.
1.1.1
Fixed
Facebook: Chrome-like Sec-* / Sec-Ch-Ua* headers, multiple URL attempts (www + m.facebook.com), parse HTML before failing on HTTP 400.
Facebook (cloud): Residential proxy for HTTP checks to reduce HTTP 400 blocks from datacenter egress.
Added
Structured English logging (src/lib/runLogger.js): section banners, Mode: phase lines, 3-space indented lines per perfect-apify-actor.
RUN_LOG key-value record (flush every 15 lines, cap 2000 lines) + Console link in output_schema.json.
Actor.setStatusMessage on Apify (throttled progress + terminal “Done” line).
.apifyignore for leaner apify push bundles.
1.1.0
Added HTTP-based availability checks for Facebook, Pinterest, YouTube (@handle), and X (Twitter).
Split Actor config: input_schema.json, output_schema.json, dataset_schema.json, key_value_store_schema.json.
Default platforms: all seven plus existing Instagram and TikTok.
Bumped default memory and optional run timeout; dataset schema extended with new columns.
1.0.0
Initial release: Instagram (web signup API) and TikTok (profile page) checks, parallel processing, residential proxy pool for Instagram.
