search

DEKHTIARJonathan / python3-linkedin

Python3 interface to the LinkedIn API
https://dekhtiarjonathan.github.io/python3-linkedin/
MIT License
84 stars 37 forks source link

LinkedIn API update #18

Open aurelg opened 5 years ago

aurelg commented 5 years ago

I just received this mail, and I guess some of you too.

The LinkedIn Developers program helps app creators and website owners provide personalized experiences to our members, gives members the ability to use their professional identity with other services, and makes it easier to share content from other sites on LinkedIn. Today, we're announcing several updates that will migrate all of our developers to the latest set of technologies used for our third-party integrations. We are also streamlining our programs, so we can provide better support to the entire LinkedIn developer community. Providing members with clarity and control over the use of their data is a fundamental priority for LinkedIn, and these changes also serve to advance this priority.

In addition to the changes listed below, all developers need to migrate to Version 2.0 of our APIs and OAuth 2.0 by March 1.

Changes to the program include:

APIs: Developers must migrate their apps to our new APIs.

  • Sign In with LinkedIn: Sign In with LinkedIn enables members to choose a more convenient way to log-in to third party apps and allows those apps to learn more about their new user. This API will only recognize a new "Lite Profile" permission, which supports a reduced set of member profile fields. See the documentation for more details.
  • Share on LinkedIn: Share on LinkedIn lets a member more easily share relevant information to their network and others on the LinkedIn platform. This API has the same functionality as before. See the [documentation]() for the new format.
  • Manage Company Pages: These APIs are being merged into the LinkedIn Marketing Developer Program and access will be restricted to those participating developers, as part of our long-term effort to provide expanded support and a better experience for marketing partners.

Authentication, SDKs, and Plugins: We are also deprecating several obsolete or seldomly-used products and technologies.

  • Authentication: We will sunset OAuth 1.0 and require all developers to use OAuth 2.0, which we have supported since 2013. OAuth 2.0 is the industry standard and widely-used by the majority of people building on our platform.
  • SDKs: Our JavaScript and Mobile Software Development Kits (SDKs) will stop working. Developers will need to migrate to using OAuth 2.0 directly from their apps.
  • Plugins: Several website plugins, which were used for generating drop-in code that could quickly add enhanced LinkedIn functionality to websites, will no longer be available for use. Specifically, the Member Profile, Company Profile, Company Insider, Jobs You Might be Interested In (JYMBII), and Alumni Tool plugins will all be deprecated.

Redesigned LinkedIn Developers portal: Along with a front-end facelift, it now gives an improved ability to access and manage apps, read documentation, and find product information.

To reiterate: all developers need to migrate their apps to our newest APIs and OAuth 2.0 by March 1, 2019. To help navigate the migration process, please see the technical migration guide on the LinkedIn section of the Microsoft Docs website. Developers can expect follow-up communications via email about these changes and other future announcements about the LinkedIn Developers program.

Thank you, LinkedIn Developers Program Team

DEKHTIARJonathan commented 5 years ago

I haven't received it. Thanks for the update.

Unfortunately I have no time to investigate which part of the library need to be updated.

If anyone wants to jump in, I'll be glad to merge a PR

wilddeej commented 5 years ago

According to the LinkedIn Migration FAQ:

All developer applications created on the LinkedIn Developer Portal after January 14, 2019 have access to the LinkedIn v2 API by default. Alternatively, if your developer application has made a successful LinkedIn v1 API request from September 1, 2018 to December 17, 2018, your developer application has immediate access to the v2 API.

No idea what that means for applications created between December 18, 2018 and January 14, 2019, however...

aurelg commented 5 years ago

I'm starting to have errors, such as:

linkedin.exceptions.LinkedInError: 410 Client Error: Gone for url: https://api.linkedin.com/v1/people/~/shares?oauth2_access_token=XXX...XX: This resource is no longer available under v1 APIs

The error message seems to indicate that the v1 API is broken. Anyway, v2 is now required. See Announcement and FAQ.

DEKHTIARJonathan commented 5 years ago

Feel free a PR, I honestly don't have the time to look at it.

Jonathan