-
Notifications
You must be signed in to change notification settings - Fork 96
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
Linkedin new version #147
Comments
I’m not fully aware of v2. Could you tell me what is stopping you from using v2 with the current client?
… On 29 Dec 2017, at 22:33, Jorge Andres Ramirez ***@***.***> wrote:
Do you have an update for the new v2 linkedin version ?
Thanks
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
We want to delete posts, here de documentation vor v2 https://developer.linkedin.com/docs/guide/v2/shares/share-update-and-delete-api#delete but we can't do it with v1, |
I found it necessary to remove the line that adds ?format=json onto the URL to talk to the ads api. ( https://github.com/Happyr/LinkedIn-API-client/blob/master/src/LinkedIn.php#L161 ) |
Sorry to jump in off-topic here. I discovered their v2 but outside their documentation center there isn't much to find (in terms of questions, chatter, etc.). Do you know how "new" it is, i.e. when it was launched or something? Just curious. |
It's still pretty new (and their documentation is pretty naff in general). From a hazy memory, I think we have to migrate from v1 to v2 sometime this year (August?). |
@DavidGoodwin did you ever find a permanently solution for this? We're in the same position |
permanent solution to what? this client not supporting v2? (we wrote a custom guzzle based client for talking to the v2 api ... so I'm not using this client). |
Same here; simply using Guzzle and manually calling the endpoints. |
@mfn @DavidGoodwin would it be possible to share some code examples for others in the same situation? It would be hugely appreciated |
There's not much to share, really. Just look at the API docs and fire up a guzzle request. |
@mfn @DavidGoodwin This is completely the wrong place to ask, but just wanted to pick your brains if that's ok? We're rolling out our own client (a forked version of this client) and the new urn structure seems very clunky. Do you know if there's a more elegant way than this to get a profile picture? $user = $linkedIn->get('/v2/me?projection=(id,localizedFirstName,localizedLastName,vanityName,profilePicture(displayImage~:playableStreams))');
$profile_picture = $user['profilePicture']['displayImage~']['elements'][0]['identifiers'][0]['identifier']; Having to delve so deep into an associative array to get the URL of a media file seems like madness. |
@scottybo I don't fetch profile data but of companies and it looks similar but not as "complex": $query = [
'projection' => '(paging,elements*(*,organizationalTarget~(id,localizedName,logo(original))))',
…
];
$result = $this->get(static::API_V2_URI . '/organizationalEntityAcls', $headers, $query);
…
foreach (…) {
… = $result[$index]['organizationalTarget~']['logo']['original'];
} 🤷♀️ |
Thanks - your projection route with stars answers some of the questions I had about that which aren't covered in the docs, so that's a big help! |
Do you have an update for the new v2 linkedin version ?
Thanks
The text was updated successfully, but these errors were encountered: