Skip to content

How to get your LinkedIn li_at cookie

Copy the li_at cookie from your browser on a computer, paste it into Connected Outreach, and keep it as safe as a password.

Updated

What the li_at cookie is

When you sign in to LinkedIn, LinkedIn gives your browser a cookie called li_at. It is your signed-in session: any browser that holds it is signed in to LinkedIn as you.

Connected Outreach uses it so your own cloud browser can work on LinkedIn as you. We never ask for your LinkedIn password.

You need a computer for this. Phone browsers don't show cookies.

Chrome or Edge

  1. Open linkedin.com and check you're signed in to the account you want to use. If LinkedIn asks you to confirm it's you, finish that first.
  2. Open the developer tools: press F12, or Ctrl+Shift+I on Windows, or Cmd+Option+I on a Mac. You can also right-click the page and choose Inspect.
  3. Click the Application tab at the top of the panel. If you can't see it, click the >> arrows to show more tabs.
  4. In the left sidebar, under Storage, open Cookies and click https://www.linkedin.com.
  5. Type li_at in the filter box to find the row named li_at.
  6. Double-click its Value cell, select all of it and copy it. It's a long string that usually starts with AQE.

Firefox

  1. Open linkedin.com and check you're signed in.
  2. Press F12, or Ctrl+Shift+I on Windows, or Cmd+Option+I on a Mac.
  3. Click the Storage tab. If you can't see it, click the >> arrows to show more tabs.
  4. In the left sidebar, open Cookies and click https://www.linkedin.com.
  5. Find the row named li_at. The filter box helps if the list is long.
  6. Double-click its value, select all of it and copy it.

Safari

  1. Turn on the developer tools once: in Safari, open Settings, then Advanced, and tick Show features for web developers. On older versions it's called Show Develop menu in menu bar.
  2. Open linkedin.com and check you're signed in.
  3. Press Cmd+Option+I, or choose Develop, then Show Web Inspector.
  4. Click the Storage tab, then Cookies, then the linkedin.com entry.
  5. Find the row named li_at, double-click its value, select all of it and copy it.

Paste it into Connected Outreach

  1. Sign in to Connected Outreach and open LinkedIn Cookie in the sidebar.
  2. Paste the value into LinkedIn session cookie (li_at).
  3. Leave Browser user agent as it is. It fills itself in from the browser you're using, so open this page in the same browser you copied the cookie from.
  4. Click Save credentials. The status changes to Not verified yet.
  5. Click the probe button on the same page to check the cookie works. Our cloud browser signs in with your cookie, opens your own profile and shows you a screenshot. It sends nothing to anyone. When it succeeds, the status turns Active.

Treat it like a password

Anyone who has your li_at cookie can use LinkedIn as you. Paste it only into the LinkedIn Cookie page in the app. Don't share it with anyone else, and don't put it in chats, emails or screenshots.

If you think someone else has it, use Sign out of all sessions in LinkedIn's settings. That makes every copy useless, ours included. Then copy a fresh cookie and paste it in.

How we store it

  • It's encrypted before it's saved, with Fernet (AES-128 with an HMAC check).
  • The encryption key sits in a separate locked file on our server, away from the database. A copy of the database alone can't reveal your cookie.
  • We never write it to logs and never show it back to you, not even on the cookie page.
  • Delete my cookie on the LinkedIn Cookie page removes it and wipes the cloud browser's LinkedIn session at the same time.

There's more on the safety page.

What makes it stop working

There's no fixed lifetime you can count on. The cookie stops working when any of these happen:

  • You sign out of LinkedIn in the browser you copied it from.
  • You change your LinkedIn password.
  • You use Sign out of all sessions on LinkedIn.
  • LinkedIn puts the account through a security check.

So once you've copied it, close the LinkedIn tab instead of signing out. When the cookie does stop working, see When your cookie expires.

Something not covered here?