-
Notifications
You must be signed in to change notification settings - Fork 97
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support of LinkedIn API v2 #167
Comments
A few notes, the library can support v2 with some special provisions:
But, the calls and the responses are different. |
+1 To this request. I've been able to mitigate the damage and am still using this API. Luckily, like the API states, it's easy to extend and you'll more than likely need to for posting for sure. Here is what I've done and hope it helps someone out in the interim. Posting content change (make sure to extend LinkedIn in whatever class you're using)
` Whatever method you're posting your content from do something similar to this (for including images, you'll need to add some custom functionality as that is overhauled from the docs I've read - haven't got to that yet): `
` LinkedIn Signing in/out. This is basically the same as what @anibalsanchez has here. // Defining explicitly what permissions we want/need - update this if we need more than this. // To get the user information (the $userInfo used to only be $userInfo['firstName']) |
It is now after March 1, 2019 and this library no longer works without overriding the hard-coded v1 uri and modding the methods. This package served me well. |
@anibalsanchez @ryanjmorris @jksteelman @andreascreten @irfanevrens |
@giovannialbero1992 : thanks for your sharing. Is your code finished / working ? |
@Florianp123 at the moment it works to retrieve information on users and post content. |
ok thanks :-) |
hi, |
hello, |
Looks like this one is dead. |
Sorry for not getting back earlier. I guess it makes sense to use https://github.com/r-everse/linkedin-php instead. |
r-everse/linkedin-php -> This repository has been archived by the owner. It is now read-only. looks like the next choice could be https://packagist.org/packages/zoonman/linkedin-api-php-client |
@c33s you may also consider this: https://github.com/SMarTStrategy/linkedin-php |
Actual Behavior
Support of LinkedIn API v1.
Expected Behavior
Support of LinkedIn API v2.
... 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.
Reference: LinkedIn v1 to v2 API Migration Frequently Asked Questions
Steps to Reproduce
Create a new App and try to use the new API v2 endpoints.
Possible Solutions
Create a new major version 2.0 of the library. It'd be great to use Happyr/LinkedIn-API-client for LinkedIn API v2.0.
Do you plan to support the new API? Or, will Happyr/LinkedIn-API-client be obsolete after March 1, 2019?
The text was updated successfully, but these errors were encountered: