LinkedIn Token Expired After 60 Days: Why, and How to Reconnect

One morning a post fails, or your assistant tells you the LinkedIn connection has expired, and nothing you did caused it. This is the single most common surprise people hit with any LinkedIn posting tool, and almost nobody explains the mechanic properly. It is worth understanding once, because once you know it you will never be caught out by it again.

Why does my LinkedIn access token expire after 60 days?

When you connect a tool to LinkedIn through OAuth (an open sign-in standard where you approve the connection on LinkedIn’s own page), LinkedIn hands the tool an access token. That is a long string which acts as a limited key: it proves the tool is allowed to act for you, but only within the permissions you approved.

That key has an expiry date baked into it. For a member token issued to a self-serve app — which is what any tool built on the free “Sign In with LinkedIn” and “Share on LinkedIn” products is using — the lifetime is about 60 days. When the clock runs out, LinkedIn simply stops accepting the key. It does not matter how often you used it, or whether you were mid-way through a campaign.

Short-lived keys are a security feature, not an oversight. A key that expires on its own limits the damage if it ever leaks, and it forces a periodic re-check that you still want this app connected to your account. The trade-off is the interruption you just hit.

What is a refresh token, and why don’t I get one?

Here is the part that explains everything else. OAuth has a second kind of key called a refresh token. Its only job is to fetch a fresh access token in the background, without bothering you. It is the reason most apps you have connected to other services stay signed in for years while you never think about them.

LinkedIn does not issue refresh tokens to self-serve apps. Programmatic refresh is a partner-tier feature: an app has to be approved into LinkedIn’s Marketing Developer Platform partner programme before it can renew a member token silently. Approval means a registered legal company, an application, and a review. It is not something a developer can switch on.

So the chain is short and there is no way around it:

• Your token lasts about 60 days.
• Self-serve apps get no refresh token.
• Therefore the only way to get a new token is for you to sign in to LinkedIn again.

What will I see when the token expires?

There is no email and no warning banner from LinkedIn. You find out in one of three ways:

• A post fails. You ask your assistant to publish, it goes through the preview and confirm steps, and then reports that the LinkedIn connection is no longer valid.
• A status check tells you. In Kalovio you can ask at any time — the linkedin_account_status tool reports whether the connection is live or needs reconnecting, and it costs you nothing to run.
• A scheduled post quietly does not appear. This is the one that stings, and it gets its own section below.

Underneath, what happened is that LinkedIn’s API answered the posting request with an authentication error instead of publishing. A well-built tool turns that into plain English rather than showing you a raw error code.

How do I reconnect my LinkedIn account?

In Kalovio it is one tool and one sign-in. Ask your assistant to reconnect LinkedIn, or call reconnect_linkedin directly, and you get back a link.

• Open the link. It takes you to LinkedIn’s own consent page. Your password, if LinkedIn asks for one at all, is typed only into LinkedIn.
• Approve the same permissions. It is the same scope as before — w_member_social, which allows publishing on your behalf and nothing else.
• You are done. LinkedIn issues a fresh token, Kalovio encrypts it and replaces the expired one, and the clock starts again for roughly 60 days.

The whole thing takes under a minute. You are not creating a new account and you are not starting over.

Do I lose anything when I reconnect?

No. Reconnecting swaps one key for another. Everything else belongs to your Kalovio account, not to the token:

The only thing that changes is the key. Your content stays exactly where it was.

Do I have to reconnect the connector in Claude or ChatGPT too?

No, and this catches people out because two separate sign-ins are involved. There are two independent OAuth connections in play, and only one of them expires here.

• Your AI app to Kalovio. This is the connector you added in Claude’s settings or ChatGPT’s Developer Mode. It is unaffected by a LinkedIn token expiring, so you do not need to remove it, re-add it, or paste the server address again.
• Kalovio to LinkedIn. This is the one with the roughly 60-day lifetime, and it is the only one the reconnect link touches.

They are deliberately never bridged — your AI app’s token is never passed on to LinkedIn, and your LinkedIn token is never handed to the assistant you are chatting with. So when a post fails on expiry, the fix is one LinkedIn sign-in, not a full re-setup of the connector.

What happens to scheduled posts if my token expires first?

This is the consequence most people miss, and it is the practical reason to care about any of this.

Scheduling works by storing your post now and publishing it later. But the publishing step needs a valid token at the moment it runs, not at the moment you scheduled it. So a post scheduled for a date beyond your token’s expiry can fail when its turn comes, even though scheduling it worked perfectly.

Think of it as a delivery booked against a permit that runs out before the delivery date. The booking is fine. The permit is the problem.

Two habits remove the risk almost entirely:

• Reconnect before a long gap. If you are about to be away, or you are about to fill the queue for the next two months, run a reconnect first. A fresh token buys you a clean 60 days from that moment, not from whenever you last signed in.
• Check the connection when you schedule far ahead. Kalovio lets you schedule up to a year in advance and queue up to 30 posts in one go. That is genuinely useful, and it is exactly the situation where a token quietly lapsing halfway through hurts most. A quick status check before a big batch is cheap insurance.

A sensible rhythm is to reconnect on the same day you do your monthly content planning. It takes less time than reading this paragraph, and it means the expiry never lands on a day when a post mattered.

Can I check how long I have left?

Not precisely, and it is worth being straight about that. LinkedIn does not publish a countdown you can look at in your own settings, and a self-serve app is told the lifetime of a token at the moment it is issued rather than given a live meter you can query later. What you can check is the practical thing: whether the connection currently works. linkedin_account_status answers that in a second.

You can also see the grant from LinkedIn’s side. Open your LinkedIn settings and look under permitted services or third-party apps — an OAuth connection is listed there, and you can remove it whenever you like. That list is also the honest proof that this is sanctioned access rather than a tool wearing your browser session as a disguise.

Will this ever stop happening?

Only if the tool you use becomes a LinkedIn partner. Partner status is what unlocks programmatic refresh, along with the other gated capabilities like engagement analytics and company-page posting. It requires a registered legal company and an app review, so it is a real milestone rather than a setting.

Until then, any honest self-serve LinkedIn tool — Kalovio included — will ask you to sign in again roughly every 60 days. The best a tool can do is make the fix a single link, keep every draft, image and scheduled post intact through it, and tell you clearly when it is needed rather than failing silently. That is the bar worth holding tools to, because the expiry itself is not theirs to remove.