This is the most common place a first connection stops, and almost none of it is a problem with the API. LinkedIn is asking the account's owner a question.
A six-digit code
From an authenticator app, a text message or an email, depending on the account. Type it into the box the dashboard shows. If it is refused, check you are reading the newest message: a code lasts about five minutes, and asking for another one retires the one before it.
A tap in the LinkedIn app
Open LinkedIn on your phone and approve the sign-in. There is nothing to type. The dashboard keeps asking on your behalf and closes by itself when it goes through — the line under the spinner tells you how many times it has asked and what the last answer was.
Anything else
- A captcha cannot be answered from an API. Use LinkedIn's own sign-in page, or a session cookie.
- A demand for a phone number has to be done on linkedin.com first.
- A restriction is LinkedIn's decision about the account, not about the password. It has to be resolved with LinkedIn.
If the window closes, the half-finished account is already in your list. Remove it there and start again — starting a third sign-in while two are pending is how people end up with an account they cannot see.