LinkedIn API glossary

The words that turn up when you start calling a LinkedIn API, and what each one actually means once you are the one handling it.

The mh_live_ string that decides which organisation you are, and therefore which LinkedIn accounts you may name.

The opaque handle for one connected LinkedIn account — and the one id in this API that is a security boundary.

LinkedIn pausing a sign-in to ask a question. The five kinds, and which ones you can answer from code.

Doing the same thing twice and getting one result — the property that makes retries and duplicate webhooks harmless.

The checkpoint with no code: LinkedIn asks for a tap in its mobile app, and nothing comes back to the request that asked.

The protocol that lets an AI assistant call this API directly, with one address and nothing to install.

Spacing calls out on purpose so an account looks like a person using it, and what that buys you.

Which address LinkedIn sees your sign-in coming from, why it matters, and when to bring your own.

Connecting an account with the cookie from a browser that is already signed in, and why the user agent has to match.

Being told when something happens instead of asking over and over — and the two things everyone gets wrong about it.