in LinkedIn API Live in production. Email, messengers & calendars next
Infrastructure
Messaging
Scraping
Enrichment data
Documentation Browse all docs →
QuickstartOne key, first call in 2 min MCP serverTyped tools for any agent API referenceEvery endpoint & schema WebhooksEvents, retries, signatures
GTM engineersConnect any agent to your GTM process AI SDRRun an autonomous SDR on real infrastructure AgenciesOnboard clients safely, run from your stack PlatformsAdd LinkedIn on proven infrastructure LinkedIn automationSafe connects, messages & follow-ups Account providersWarm, secure & lease account fleets
Pricing Blog
LinkedIn shadowban checkerDo your invitations still arrive? A two-minute check All free toolsSmall checks that run without an account
Get API key Sign in
Free tools

LinkedIn shadowban checker

Send one connection request to a profile we name and read within two minutes whether it arrived. No account, no extension.

One check per profile every 30 days. We keep the handle from your URL and the result, nothing else. No login, no extension.

Connect your account on the free plan and the check runs itself

Every account connected to gtm-api.com gets this delivery probe automatically on its first sync, before the first campaign. No card.

Connect an account

How it works

Three steps, one invitation, a verdict you can read the same way we do.

01

Paste your profile URL

We only keep the handle from the URL (the part after /in/) and the result. No login, no password, no browser extension.

02

Send one connection request

We show you one of our own LinkedIn profiles. Open it from your account, press Connect, then come back and press "I sent the request". No note needed; the invitation itself is the test.

03

Read the verdict

From that click our side reads that inbox once a minute for two minutes. Arrived means sending from your profile works. Not arrived means it did not reach us inside two minutes, and the page lists the ordinary reasons to rule out before the interesting one.

What this measures, and what it does not

This tool reports one thing: whether a connection request you send arrives in an inbox we control. That is a delivery result on our own side of the wire, read once a minute for two minutes, and it is the whole of what we can see. We cannot see how an account is ranked or how its content is distributed, and we do not infer either from a delivery result. What people mean by a shadow ban, and what the platform itself publishes about it, is set out with its sources in the LinkedIn shadow ban guide.

It cannot see whether your posts are being shown less, and it cannot tell a dropped invitation from one you never sent. So read the result as one line of evidence. Arrived rules out the loudest fear: your account can still send and be received. Not arrived is worth taking seriously only after the mundane causes are excluded, and the page tells you which ones. For the full diagnosis, the search test, the impressions baseline and the recovery sequence, read the LinkedIn shadow ban guide.

What a LinkedIn shadow ban is

"Shadow ban" is the informal name people give to reach that falls with no notice. It is not our term, and it is not a state our API can read: nothing in a delivery result tells us how an account is ranked or what its content reaches. The full read, with the platform's own sources and the difference between this and a restriction that announces itself, is the LinkedIn shadow ban guide. This page stays with what the probe measured.

The symptoms arrive in a fixed order. Invitation acceptance falls first, replies dry up second, post impressions sag last, and sending itself keeps working the whole time, which is why this tool tests delivery rather than reach. Each symptom has a boring explanation that is more common than filtering: targeting drift, a slow week, a format change, a weekly limit you never noticed. The pattern that matters is several of them together, sustained over weeks, with no other cause in sight. The symptom table pairs each one with its other explanation.

What precedes it is read backwards from what accounts did shortly before reach fell: invitations piling up ignored and then withdrawn in one sweep, bursts of automated activity, engagement pods, a reported post. The trigger list is in the guide.

The way back is unglamorous. Stop every automation on the account, clear the invitation debt oldest-first over several days, spend two to three weeks engaging manually from the usual device, watch impressions against the pre-sag median rather than your best month, and only then resume on a warm-up curve. Community reports cluster around two to four weeks before reach normalises. The recovery sequence spells out each step, and a second run of this check a month later tells you whether delivery came back with it.

Questions people ask before pressing Connect

What happens to my profile URL?

We store the handle from the URL, the profile we asked you to write to, the timestamps and the result. That is what makes the once-a-month rule and the verdict possible. We do not log in to your account, do not read anything else on it, and never send anything from it. The connection request you send is yours; you can withdraw it afterwards from your Sent invitations.

Why one check per profile a month?

Because the test costs a real invitation on your side and a real inbox read on ours, and because a profile that fails today and passes in an hour has learned nothing. A month is long enough for a recovery sequence to show. If you started a check and left, coming back while it is still running resumes the same check.

It says not arrived. Am I shadowbanned?

Not yet. Four things produce the same result and are far more common: you pressed Follow instead of Connect on a profile in creator mode, you closed the tab before the request went out, LinkedIn showed you its weekly invitation limit (it shows that message to you, not to us), or you already had a pending invitation to that profile from before. Rule those out, then read the recovery sequence in the guide.

It says arrived, but my acceptance rate is still terrible.

Then delivery is not your problem, and that is useful to know. Invitations that arrive and sit unanswered are about who you write to and what the profile looks like when they open it, which is a different fix from a visibility problem. The guide covers both.

Who receives my connection request?

One of the LinkedIn accounts our own team runs on gtm-api.com. You will see the name and the profile before you send anything. We do not accept or decline the invitation as part of the test; it just needs to arrive.

What is a LinkedIn shadow ban?

The informal name for reach that falls with no notice. It is not a state we can query and not what this tool measures: we report whether your invitation arrived on our side, and nothing beyond that. The guide has the sources, the full picture, and what a restriction is and how it announces itself.

How long does a LinkedIn shadow ban last?

LinkedIn publishes no duration. Community reports cluster around two to four weeks of ordinary, manual activity before reach comes back. If a month of clean behavior moves nothing, stop calling it a shadow ban and look for an official restriction state, which shows up on screen or by email.

How do I get out of a LinkedIn shadow ban?

Stop every automation on the account, withdraw stale pending invitations oldest-first over several days, engage manually for two to three weeks from your usual device, post on your normal rhythm and compare impressions against the pre-sag median, then resume on a warm-up curve at a fraction of the old volume. The recovery sequence in the guide goes step by step, and running this check again a month later tells you whether delivery came back.

Do connected accounts get this automatically?

Yes. Every LinkedIn account connected to gtm-api.com runs the same delivery probe as soon as its first sync completes, from the account itself, so a sender that cannot reach anyone is caught before the first campaign rather than three weeks into one.

Connected accounts are checked automatically

Every account you connect to gtm-api.com runs this delivery probe on its first sync, and keeps running under smart limits, a warm-up curve and an isolated cloud browser. Free plan, no card.

Connect an account