LinkedIn – Have you migrated to our new v2 APIs?

About 10 days ago I received an email from Linkedin, asking if I have migrated to their v2 API, so I’m making this post to notify you guys and remind you about it.

linkedin-have-you-migrated-to-our-new-v2-APIs

Dear LinkedIn Developer –

Many of you have already completed migration to our new V2 APIs. For those that still need time, we are extending the previous deadline to migrate your existing applications from v1 APIs to our new v2 APIs.

The new deadline is May 1, 2019.
(If you are one of the few developers using our JavaScript SDK, this extension does not apply.)

To see which permissions are included in the new v2 platform, or if you need assistance, please refer to our Self-Service Program v2 Migration Guide. In particular, you must request only our new member permissions; otherwise, after we disable our legacy permissions, your application will break during the OAuth flow.

You will need to integrate with our v2 APIs by May 1st, in order to avoid breaking your application. After May 1st, our v1 APIs will cease to be available.

Thank you,
LinkedIn Developers Program Team

 

Personally, I don’t really know much about API and all that kinda stuff, but I do make use of Linkedin’s API for some WordPress plugins I use for autoposting on Linkedin. So I’m not really writing this post for people like me, but for people that actually work with the API and all that, the developers of apps and plugins.

Guys, developers, please update your stuff.

You can see in the email Linkedin was nice enough to give an extension on their original deadline, so that gives you more time to migrate everything nicely, so that our autoposting plugins and other things that use the Linkedin API continue to work without bugs and interruptions 😀

Here is a video I made about the situation:

Share the Love!

Shares

Leave a Comment