Why a LinkedIn invite returns a 403: Sales Navigator member IDs explained

If a LinkedIn invite fails with 403 feature_not_subscribed while messages and likes on the same account still work, the session is fine and you have not hit a limit. Look at the lead ids. Ids that start with ACw are Sales Navigator member ids, and only an account with Sales Navigator can invite by them. The classic id, starting with ACo, works for any account.

This is a first hand explanation. We found it while debugging a customer account whose invites failed for hundreds of leads while everything else worked, and the answer was not in any documentation we could find. If you build or run LinkedIn automation, it can save you days.

What does the error look like?

A request to send an invitation returns HTTP 403 with an error of the form errors/feature_not_subscribed. The account is connected and healthy. It can read conversations, send messages to existing connections and like posts. Only invites fail, and not all of them.

The usual first suspicions are all wrong:

• A broken session. If the session were bad, messaging would fail as well.
• A LinkedIn limit. An invitation limit or a restriction on sending invitations produces different errors, and it hits every invite, not a subset. See LinkedIn invitation limits.
• A restricted account. LinkedIn's own message about a restriction is different. See what to do if LinkedIn restricts your account.

What is the real cause?

LinkedIn identifies members with an internal id. There are two forms in practice.

• Classic member ids, which start with ACo.
• Sales Navigator member ids, which start with ACw.

When you run a search in Sales Navigator and import the results, the leads carry Sales Navigator ids. An invite addressed to that kind of id can only be sent by an account that has Sales Navigator. An account without it gets 403 feature_not_subscribed, because from LinkedIn's side that account is using a feature it has not subscribed to.

That explains the pattern: the same account can invite leads that came from a normal LinkedIn search or a CSV with profile URLs, and fails on leads imported from Sales Navigator. It also explains why a team with one Sales Navigator seat can invite from that seat and not from the others.

How do you check it?

1. Open a few leads that failed and look at the member id stored for each.
2. If the ids start with ACw, you have found it. If they start with ACo, the cause is something else.
3. Compare with a lead that worked on the same account. It will usually start with ACo.

If you use another tool, look for the id in the lead record or the export. If you cannot see ids, check where the failing leads were imported from.

How do you fix it?

Two routes.

Resolve the classic id. Look the person up by their public profile slug, using the same connected account. The lookup returns the classic id, which starts with ACo. Invite with that id. It works from any account, with or without Sales Navigator.

Or import differently. Use a source that stores classic ids or public profile URLs, and keep Sales Navigator for searching only.

What does Sellinger do?

Our LinkedIn worker resolves the classic id before it invites. A lead imported from a Sales Navigator search can therefore be invited from an account that does not have Sales Navigator. We found it on 14 October 2026 on two customer accounts with thousands of leads between them, fixed it in the days after, and confirmed on 17 October that invites were flowing. In the 30 days before the fix, accounts without Sales Navigator had no contacted leads that carried an ACw id, which fits the explanation: the error stopped invites before they were ever sent.

Converting the ids at import time is still on our list. For now the conversion happens at the moment of the invite.

Does it mean you need Sales Navigator?

No. You need it if you want its search filters, saved searches and alerts. You do not need it to send invitations, as long as the invite uses the classic id. For how the two compare with a lead database, see do you need Sales Navigator or a lead database.

What other 403 errors might you see?

A different 403 with a message about restricted resource access means LinkedIn is refusing a feature for that account, for example reading a person's posts. It is a platform restriction, not an id problem. A sensible tool pauses that feature for a while instead of repeating the call, because hammering a feature LinkedIn has already restricted risks escalating the restriction. Our engagement worker does that, pausing a seat for 24 hours after three of them in a row. Do not retry in a loop.

Why do the ids differ at all?

We read the two forms from the data, not from a LinkedIn document, so treat the explanation as what we observed. Leads imported from a Sales Navigator search carried ids starting with ACw, and leads from normal profile URLs carried ids starting with ACo. The account with no Sales Navigator got the 403 only on the first kind. That is enough to act on, and it is why we say "in practice" about the two forms.

What does a made up triage look like?

An example of the check, with invented numbers. A team connects one account and imports 800 leads from a Sales Navigator search. After a day, messages to existing connections work, but 0 of 120 invitations have gone out and every attempt returns 403 feature_not_subscribed.

1. They open five failed leads and see ids that start with ACw.
2. They open one lead imported from a CSV of profile URLs. Its id starts with ACo, and its invitation went out.
3. They conclude that the id kind, not the session, is the cause.
4. They resolve the classic id from each public profile slug, or re-import the list from profile URLs.

The check replaces days of suspecting the session, the limit and the proxy.

What if the id starts with ACo and it still fails?

Then it is a different problem. Check, in this order:

1. The weekly limit. If invitations stopped after a number of sends, look at the cap and at invitations sent outside your tool (how to spot invites sent outside your tool).
2. A restriction notice. If LinkedIn showed a prompt or a restriction, stop sending and follow what to do if LinkedIn restricts your account.
3. The lead record. Check that the person is not already a connection or already invited, and that the profile still exists. Those are data problems, not account problems.

Which question should you ask a vendor?

If you use a tool that imports from Sales Navigator, ask how it handles the member id when the connected account has no Sales Navigator. The answer should be that it resolves the classic id before it invites, as ours does. If the answer is "you need a Sales Navigator seat on every account", that is a cost you can count before you buy. See do you need Sales Navigator or a lead database.

A short troubleshooting list

• [ ] The account can message and like, only invites fail.
• [ ] The failing leads came from a Sales Navigator search or import.
• [ ] Their ids start with ACw.
• [ ] I resolved the classic id (ACo) with the public profile slug.
• [ ] If ids are classic and invites still fail, I check limits and restrictions next.