Reference/Pull Linkedin Profile Picture

4 posts / 0 new
Last post
Xuan Ho's picture
Joined: 02/17/2012
Tue, 02/21/2012 - 07:20
Reference/Pull Linkedin Profile Picture

Hi,

I am new to LinkedIn API, I have done some initial research but I have a few questions.
I would like to be able to reference or pull a member's Profile Picture into our local application contact profiles so that each time
I view the contact's record I will be able to see his/her LinkedIn profile picture.

1) Is it correct, that I can only reference the LinkedIn profile picture for display?
If referencing the picture, I do not need to obtain individual authorization.

If I want to pull the profile pictures and store them on a local database, I would
need to obtain authorization from each member whose picture I intend to store?

2) After using my profile to connect, can I only reference/pull profile pictures from members that are within my network
or can I also reference/pull pictures for people outside of my network?

Thanks in advance!

Jeremy Johnstone's picture
Developer Advocate
Joined: 04/17/2011
Tue, 02/21/2012 - 20:48

Hi Xuan,

The user who is being shown the photo must authenticate with LinkedIn, otherwise you won't be able to call the API to get the picture URL. You aren't permitted to use the same authentication credentials for all users. As long as the user who is viewing the photo is authorized, you can then show photos for anyone that the API returns a value for, whether the user is in network or not (the API won't return the picture URL for users who's privacy settings don't allow it).

-Jeremy

Kirsten Jones's picture
Joined: 06/30/2011
Wed, 02/22/2012 - 08:54

Additionally, please note that you can *not* store data in your database unless it is profile information for the user who has authenticated and you explicitly tell them that's what you're doing. This means you can't store any information about the user's connections, search results, or any other user in our system.

Xuan Ho's picture
Joined: 02/17/2012
Thu, 02/23/2012 - 05:17

Thanks both for the clarification.