Skip to content

Conversation

@venkatesh2100
Copy link

The validator:
Requests the public profile URL: https://www.linkedin.com/in/{username}/
Does not follow redirects to avoid triggering additional anti-bot checks
Common block responses include status 999, 403, and 429

  • Error handling

Result.error("blocked (linkedin)") is returned intentionally when LinkedIn blocks or rate-limits the request.

@kaifcodec
Copy link
Owner

@venkatesh2100 Thanks for the PR, it looks clean and well structured. However, when I tested it locally, it always returned a 999 status code, which is expected behavior from LinkedIn servers. LinkedIn requires a CSRF token in the request headers, and as a CLI tool it’s tricky to dynamically fetch that token and correctly craft the required headers. Because of this, the current approach won’t work reliably for us.

If we’re able to discover an undocumented or private API that LinkedIn uses for username availability checks, then this could be made to work. If you’re interested in exploring that (it’s a little advanced task), feel free to keep the PR open and push further commits if you find a solution.

Otherwise, you’re welcome to pick up any of the good first issues to work on in the meantime.

@kaifcodec kaifcodec added bug Something isn't working need-extra-changes Some files or parts of the code may require additional edits or updates for it work properly. labels Dec 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working need-extra-changes Some files or parts of the code may require additional edits or updates for it work properly.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants