LinkedIn r_basicprofile only returns current position, not past positions

Question

While it would seem to be a bug, it's always been true that LinkedIn's r_basicprofile API permission only returns the user's current positions, while r_fullprofile returns current and past positions. But with today's announcement that r_fullprofile will require enrollment in LinkedIn's partnership integration program, this difference has a real consequence: Many LinkedIn-integrated sites will no longer be able to get past positions.

My question is to LinkedIn API folks: Is it deliberate that past positions are not returned for r_basicprofile requests? Hopefully not, and hopefully this could be fixed. Alternatively, three_past_positions could be enabled for r_basicprofile... That'd give us something to work with.

If everything is working as intended, and no changes will be forthcoming, how difficult will it be to join the partnership program? Do you foresee many companies and start-ups being able to join?

Thanks!

Dodiedodo

Answer 1

I think that @JoseR answer was extremely close... the part that was missed was that of within the 'field' description it states:

positions -> An object representing the member's current position https://developer.linkedin.com/docs/fields/basic-profile

so, if the member has ten 'current' positions, it will return ten, but if they only have one, then just one is returned... so, to get the r_fullprofile is your next best option (with application of course)

Intemerate

Answer 2

As we can see in https://developer.linkedin.com/docs/fields/basic-profile is supposed that now in the basic profile we are going to get all the positions, at least it does not say anything about any restriction to the current ones.

But please I'm +1 in this question. It would be good to have some confirmation from the linkedIn staff that, when accessing the new API, we are going to get all the positions.

Thank you.

Eure

We do not get all the positions. We only get the user's current position. That's what the documentation says, and that's what happens. – Dodiedodo

That is not what the doc said when they announced the new API changes. They are managing this poorly, – Eure