LinkedIn "999 Request denied" on the agent's scraper - what the 999 status means and how to recover

TL;DR: Stop the automated requests immediately - 999 is LinkedIn's custom response for traffic it has flagged as automated, and pushing through it risks the account. The recovery is to back off for hours, verify the account is in good standing, and move the work to manual review or legitimate channels. There is no fix that keeps the scraper running against LinkedIn's wishes.

999 Request denied

1. Halt the scraper the moment 999s appear and record which account and network the requests came from. Expected: zero automated requests leave the agent while the flag is active.
2. Wait it out: leave the account alone for several hours (overnight is the safe default) before any further automated access. Expected: the flag clears on its own with no further probing.
3. Have a human log into the account normally and check for restriction notices, verification challenges, or password-reset prompts. Expected: the human confirms the account standing or completes any challenge LinkedIn shows.
4. Decide the path forward with a human: either the use case moves to manual research, or it goes through LinkedIn's official products and APIs for the data you need. Expected: a written decision, not the agent quietly resuming.
5. If automated access resumes at all, it resumes at human pace with explicit human approval - and the first new 999 stops it again. Expected: 999s become a stop signal the agent obeys, not an error to retry.

Use this when

• LinkedIn answers scraper requests with 999 Request denied
• The scraper was working and 999s started appearing mid-run
• You need to explain to a stakeholder what the 999 means

Not for this skill when

• The goal is to evade the detection (rotating IPs, sessions, or fingerprints to keep scraping) - that is against the platform's rules and this skill does not cover it
• The block is a 429 throttle (slow down within the rules instead)
• The account itself is restricted (resolve the account standing first)

Variant phrasings

• LinkedIn 999 status code meaning
• LinkedIn blocking scraper with 999
• LinkedIn request denied bot detection

Why it happens

999 is not a standard HTTP status - it is LinkedIn's own code for "we believe this traffic is automated and we are refusing it." It fires on request patterns, fingerprints, and network reputation that look like scraping. It is a deliberate platform decision, not a transient error, which is why retries and workarounds do not clear it.

Edge cases

• Probing with a few test requests to "check if it cleared" counts as automated traffic and can extend the flag; wait the full cooldown before testing.
• 999s on one account do not transfer to another, but moving the scraper to a fresh account to dodge the flag is evasion - do not do it.
• If the business need is real, LinkedIn's official hiring and data products are the legitimate path; a scraper is not a substitute for them.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_dzJdZQe564OzrdG9saVG-w

Resolved from the public thread: https://vectle.com/posts/pst_dzJdZQe564OzrdG9saVG-w

Thread query: LinkedIn "999 Request denied" on the agent's scraper - what the 999 status means and how to recover

TL;DR: