We will not scrape LinkedIn inboxes

We will not scrape LinkedIn inboxes. Official API and public pages only. This commercial query gets a line, not another tool list. The automation desk already skipped the clickers on LinkedIn automation tools we refuse. This URL skips the harvest.

I write it as a local Windows note, not as a growth-hack companion to the company-page article.

What official looks like here

A Recruiter or Sales Navigator seat you pay for. Campaign Manager for ads you run. The official API and partner program when your job is data. Page roles for people who should post. Public pages a signed-out person can read.

Official APIs versus headed collection. If LinkedIn published a door for the bytes, use that door. If they did not publish a door for InMail and inbox HTML, there is no research version of that scrape.

LinkedIn research on public pages is the look. Company pages and Sales Navigator stay licensed. Isolation is for work you already pay for. A local profile holds the licensed login. It does not become a parser.

What an inbox scraper is

A tool that pages messages, connection graphs, or profile lists you were not given an API for. It wants a session, a cookie, or a headed cloud browser. It writes a CSV of people. That is personal data collection with a sales hat. Scraping behind a login is not research.

A product that advertises LinkedIn inbox packs fails permission on the first screen. How to judge a web scraping tool. I will not name the packs.

A headed collector pointed at messaging is still a collector. An exit will not turn into a license.

Instagram is the sibling query

Instagram public research versus a scrape is look versus harvest on another network. Same ethic. Different URL because people search it that way. The Python overview will not grow a LinkedIn inbox chapter either. Web scraping with Python, without a stealth stack.

What web scraping is and scraping ethics we follow are the parent notes. LinkedIn's terms are not a footnote we skip because a tool is popular. robots.txt and terms come first.

What a local profile is still for

A company admin you are allowed to use, on one PC, isolated from a personal cookie store. You read the inbox as a person. You export through a button LinkedIn already ships, if it ships one for your seat. You store that export off the work profile. Storing research files.

You do not attach Playwright. You do not load an unofficial helper as an unpacked extension. You do not mail maskwright-cookies.json to a vendor. That file is plaintext. The live user-data directory is not encrypted by our code.

MaskWright 0.1 isolates profiles. It has no LinkedIn integration, no RPA, and no collection API. Bulk start opens licensed profiles. It does not walk an inbox.

A captcha or a wall on a paging client is a stop, not a product idea.

What I will not add to be helpful

A comparison table of inbox tools. A "research only" selector guide. A cookie-hygiene note that is actually a pipeline. A Sales Navigator workaround that is a scrape.

If you need the data, you buy the seat, you apply for the API, or you do without. Those are the honest options.

A recruiter who already pays for Recruiter still reads InMail as a person. The seat is not a scrape license. A sales lead list that only exists because a helper paged profiles is a list we will not help you build. Write the outreach yourself, from people you already have a right to contact, or use the official tools LinkedIn sold you.

The commercial query will keep offering a table of inbox tools. Close it. The line is the article.

If a teammate forwards a "safe LinkedIn scraper" thread, reply with the official API docs and the public-pages note. Do not evaluate the tool on stealth. Evaluate the job. Inbox HTML is not a job this cluster will take.

The Scraping hub is a stack of lines that still leave authorized work intact. This page is the LinkedIn inbox line. Official door, public look, or stop.

FAQ

I already pay for Recruiter. Can I export InMail with a script?

Read messages as a person. Use an official export if the seat ships one. A script paging the inbox is still a harvest.

Is a local profile a safer inbox scraper?

No. Isolation keeps a licensed login apart from a personal feed. It does not turn messaging HTML into a dataset.