How to use v2?

[itaydressler]

Hey, thanks for this lib!

I want to use the v2 lib version in order yo use linkedin v2 api.

1. How do I install it via npm? is it published there? I managed to install it only via the git link (npm install https://github.com/ArkeologeN/node-linkedin.git#v2.0 --save).
2. How do I use it after installing? the index.js file is empty, so when I require the file it returns an empty object.

Any help would be greatly appreciated 🙏

[ArkeologeN]

@itaydressler it is under-development and not recommended (available) for production use :)

[kartboy16]

Looks like LinkedIn is forcing everyone to use version 2.0 by March 1, 2019.

https://engineering.linkedin.com/blog/2018/12/developer-program-updates

[YasharF]

@ArkeologeN do you have any updates on the v2 release? I noticed that the link by @kartboy16 is stating

To reiterate: all developers need to migrate their apps to our newest APIs and OAuth 2.0 by May 1, 2019.

[captainjackrana]

I've forked the library and made some changes to allow Oauth and basic profile fields fetching to work. Till the time the author officially makes the changes to the library, anyone looking for just basic functionality can use the forked git package for now
npm install captainjackrana/node-linkedin --save

Calls that work as of now -

• linkedin.people.me - fetches Liteprofile
• linkedin.people.email - fetches emailAddress

[yashmurty]

Thank you @captainjackrana.
Any timeline for when this repository would also update to v2? @ArkeologeN

[YasharF]

@yashmurty or other folks that are seeing this GitHub issue. Access to the original APIs that LinkedIn had, has been mostly removed by them. This is similar to the transition that the rest of the social media providers such as Facebook has been going through to not allow access to the data of users on their platforms. In other words, what node-LinkedIn did is considered mostly inaccessible as well. The APIs that LinkedIn provides is now mostly for their enterprise customers that have paid sales or recruiting subscriptions and listed at https://www.linkedin.com/developers/products.

What are the use cases that are driving developers to want a v2 of node-linked?

[yashmurty]

@YasharF Thank you for the prompt reply.

What are the use cases that are driving developers to want a v2 of node-linked?

The primary reason why asked for the migration is because when I tried to run :

linkedin.people.me(function(err, $in) {
    // Loads the profile of access token owner.
});

It returned with the following message:

{ errorCode: 0,
message: 'This resource is no longer available under v1 APIs',
requestId: '****',
status: 410,
timestamp: 1564501688370 }

Hence I was asking if there is any plan to migrate to v2.

[YasharF]

LinkedIn with v2 is no longer providing most of the data that linkedin.people.me provided. The data that is now accessible is with the scope: ['r_basicprofile', 'r_emailaddress'] as the response of the OAuth call, which includes only the user's name, profile picture URL, and email address (https://docs.microsoft.com/en-us/linkedin/consumer/integrations/self-serve/sign-in-with-linkedin). As long as you have a way to do an OAuth call, then there is no need for use of node-linked.

Lack of access to the user's profile is not because of upgrading this project to V2. It is that V2 from LinedIn's end does NOT provide the user's profile. It was a decision made by LinkedIn's owner, Microsoft, to remove the access. See:

• https://developer.linkedin.com/docs/guide/v2
• https://docs.microsoft.com/en-us/linkedin/consumer/integrations/self-serve/migration-faq
• https://docs.microsoft.com/en-us/linkedin/consumer/integrations/self-serve/sign-in-with-linkedin

[yashmurty]

As long as you have a way to do an OAuth call, then there is no need for use of node-linked.

@YasharF Thank you for your comments. 🙏
If there is no plan to update this project to v2 then using node-linkedin to get user profile will no longer be feasible. But I'd like to hear the author @ArkeologeN thoughts on this.

[sanozie]

@ArkeologeN any updates on this issue?

[subodhk01]

Any updates on the v2 library??

[captainjackrana]

For people looking for an alternate library, I've switched over to node-linkedin-v2
Seems to be working fine, might need to write a couple of wrapper functions on top for additional customizations.

[subodhk01]

@captainjackrana But there is not documentation provided for this library, even though the source code is pretty self explanatory but still

[YasharF]

@subodhk01 what is it that you are trying to do which you feel a v2 library would be able to solve?