fix(instagram): replace broken web_profile_info with signup-attempt endpoint#328
Merged
kaifcodec merged 1 commit intokaifcodec:mainfrom Apr 24, 2026
Merged
Conversation
…attempt check The web_profile_info API now returns 401 for all unauthenticated requests, breaking Instagram username scanning entirely. Switch to the signup-attempt endpoint (web_create_ajax/attempt) which reliably indicates username availability without requiring authentication. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Contributor
Author
|
Verified this fix works end-to-end — ran a bulk scan of 41 usernames and Instagram checks returned correct results for all of them (e.g. |
kaifcodec
approved these changes
Apr 24, 2026
Owner
kaifcodec
left a comment
There was a problem hiding this comment.
@anonymort Thanks for the update, this approach is more reliable as it directly checks the username availability using the account creation flow.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
web_profile_infoAPI endpoint now returns401 Unauthorizedfor all unauthenticated requests, causing every Instagram username scan to fail with[401] Status didn't matchweb_create_ajax/attempt), which reliably reports whether a username is taken without requiring authenticationusernameerror with codeusername_invalidorusername_is_takenif the name is taken, and no username error if it's available. CSRF validation only checks that the header matches the cookie value, so a dummy token ("0") works without an extra preflight requestTest plan
instagram,cristiano,bonniebop) report Foundxyznonexistent99999) report Not Founduser-scanner -u <name> -m instagram🤖 Generated with Claude Code