How get Email from user profile?

161 posts / 0 new
Last post
Jeremy Johnstone's picture
Joined: 2011-04-17
Feb 14, 2012

Hi James,

I don't feel there is much for me to respond to that I haven't already, but one point I will add is that if you are required by law to validate the accuracy of user data, I'm baffled how getting the data from a 3rd party source would meet that burden on face value. That said, I am not personally versed on the specific law you mention (aware of it, but haven't analyzed it in depth) and I am not a lawyer, so take this response with a grain of salt.

-Jeremy

Kristof Pelckmans's picture
Joined: 2011-11-18
Feb 15, 2012

Hi Jeremy,

Did the test on my connections and got 0.584% of all my contacts who have a LinkedIn specific address. Curious to hear from other people in this thread how many e-mail addresses are LinkedIn specific.

In fact, it is very easy to check. Just go to http://www.linkedin.com/addressBookExport, export to CSV and search for addresses that contain linkedin.

The other argument that Kirsten used was the fact that users can have multiple e-mail addresses. I think that the primary e-mail address could be sufficient to begin with, just like
- the LinkedIn address book exports one e-mail address
- the "apply with LinkedIn" uses one e-mail address (see screenshot on https://developer.linkedin.com/apply-how-it-works)

That said, I think it is a bit disingenuous to reveal all of the user's phone numbers but to keep insisting to hide the e-mail address(es).

Hope eventually you will find some time to fix this,

Kristof

James Cridland's picture
Joined: 2011-10-09
Feb 15, 2012

Kirsten, thank you for responding.

In my experience, linkedin@mydomain.com - or me+linkedin@mydomain.com - will still reach me, and gives me an understanding of how this particular emailer got my email address. The point is that it's a valid - and checked - email address to get in touch with me. That complies fully with a requirement to have up-to-date information about someone. If your user is using an email address which doesn't work, then the user isn't getting any benefit out of LinkedIn either.

As a developer, I am unconcerned whether this email address matches with Facebook or Google, since users generally sign in with the same service. The goal is not to aggregate user information; the goal is to offer a simple, straightforward login - with a valid email address - using a service they already use.

My understanding from previous posts in this thread is that LinkedIn refused on a point of principle to ever share email addresses of users over OAuth - and has spent a long time in this thread arguing against the principle of doing so. Your response is rather more helpful, and less dogmatic.

Incidentally: "our product manager works very hard to assign resources based on the current priorities of our developers" - your product manager should be prioritising based on your users, not your developers! ;)

Joined: 2011-02-13
Feb 15, 2012

"your product manager should be prioritising based on your users, not your developers! ;)"

+1

Alexander Donnelly's picture
Joined: 2012-02-16
Feb 16, 2012

I'm new to the developing game, but linkedin's inability/refusal/whatever about disclosing email addresses is very frustrating. I understand that this may be purposeful, but based on the responses you have received here, maybe it would be in the best interest of linkedin to respond to the market and allow the sharing of email.

Further, and this is directed more at Jeremy, the developers represent your site; being rude or short with people is not good for business, nor does it make for happy customers/developers.

“So I assume you can't implement SSO for Twitter either then for the same reason? All because of your "dogmatic" (to use another poster's word) refusal to add a single text entry field requesting the user's email address?”-Jeremey

If something is outside your control (as this seems to be, I understand you cannot change policy), it might be helpful to follow up with an email address or a phone number we can all voice our concerns and suggestions to. We developers are trying to work with you, not against you. The easier it is for users to log in with linkin to our sites, the more users you will get in return, and the more your business will grow. We're all just trying to help each other out.

At any rate, can you provide a contact within linkedin that we can address our concerns to? I would be happy to speak with a product manager or someone else who sets these policies

Thanks!
Alex

James Cridland's picture
Joined: 2011-10-09
Feb 16, 2012

Great response, Alexander.

For clarity: "maybe it would be in the best interest of linkedin to respond to the market and allow the sharing of email." ON A CASE BY CASE BASIS WHEN THE USER AGREES TO IT is what we're asking for. We're not asking to spam LinkedIn users.

And it's notable that Jeremy has failed to contact me by email; and left this topic to the infinitely more helpful Kirsten.

Joined: 2011-02-13
Feb 17, 2012

James,

I thought you'd appreciate this link. As you correctly pointed out, the customers should set the priorities, not the developers.

http://hal2020.com/2012/02/15/dear-developer-excuse-me-while-i-slap-you-silly/

Joined: 2011-10-23
Feb 17, 2012

I can understand the strategic purpose behind this and some other API features (like appending a LinkedIn logo to user photos) but this creates a poor user experience for users trying to register with LinkedIn. Like others have mentioned, email is frequent unique identifier. It's easier to remember for people than a username.

LinkedIn should do what Facebook does. Explicitly tell the user that their email is being requested. It's very simple.

I can work around this but sucks making registration more painful than it has to be. What's even more hilarious about this is LinkedIn uses email as a unique identifier, too.

Joined: 2011-10-23
Feb 17, 2012

Poor grammar above... my bad. Typed it out pretty fast.

John Whelan's picture
Joined: 2011-12-28
Feb 19, 2012

I too am working on a b2b application where the inability to capture the user's email address through the LinkedIn login button is making me irritated. Come on LinkedIn people, you have to understand where we are coming from. Authorization without the user's email address is a poor second best. Why not step up on this issue for the community?

Samuel Deering's picture
Joined: 2012-02-06
Mar 19, 2012

I'm looking forward to LinkedIn sorting out their API and providing access to the email address without having to make a separate request.

Kirsten Hunter's picture
Joined: 2011-06-30
Mar 20, 2012

Trust me, I understand your frustration. Note that LinkedIn's website is all about what users want and need, but our API is designed to be usable by our developers. So the product manager for the API has as a main goal (as everywhere else in LinkedIn) the user experience, but our team is specifically targeted at making sure that developers can create applications.

Our product manager is aware of this request, and while we can't comment on future functionality I can assure you we've been discussing ways that we can make this available without surprising our users. Remember that our primary consideration is that nothing happens that the user isn't expecting, and our current permission model does not provide enough information to our users to give them information that people might get their email address. And while I understand that in a perfect world we could snap our fingers and make the change, creating new functionality takes time.

Thanks to our community for your empassioned arguments on the topic and your patience while we make sure that anything we implement upholds our most core company value - protecting our users' identity.

nirav patel's picture
Joined: 2012-03-27
Apr 2, 2012

please help me to get email using linkedin api..

Joined: 2011-12-11
Apr 4, 2012

I think this will be a comment against the LinkedIn API for many developers, like me, as long as you do not give out the user email address.

Joined: 2012-03-27
Apr 15, 2012

I also hope linkedin provider the user's email

Pavan Lulla's picture
Joined: 2012-03-26
Apr 16, 2012

I would like to add my support for exposing E-mail in the API, at least conditionally if they want to be taken seriously.

I would suggest Linkedin simply admit their flawed thinking and fix it quickly, rather than beating around the bush. I do appreciate it is a major change.

David Mehrania's picture
Joined: 2012-04-16
Apr 17, 2012

Well! I just spent a few hours of reading through documentation and implementation only to find out that I can't even get access to Linkedin user's email address which is vital in authentication against our local database. Just wondering why Linkedin couldn't display a simple message informing the user that the application is requesting user's email address. User always has a chance to bail out. Facebook has implemented that work-flow and it works quite nicely.

I am trying to wrap my mind around the fact that Linkedin decided that user's phone number and DOB are not as sensitive as email address! Really? I only read through some of the earlier posts on this long thread and it seems like I am not alone on this.

I am sorry for sounding a little rude, but I hope you understand my frustration for wasting a perfectly good few hours of my time. I hope Linkedin reconsider this limitation.

Thanks,
David

Jackson Carson's picture
Joined: 2012-03-13
Apr 18, 2012

We're in the same boat. We are excited to capitalize on LinkedIn's well-earned position as a business service to authenticate into our business app. Since our app (and most others I'm familiar with) require an email as the GUID for the user, how is LinkedIn authentication even a viable option in the marketplace? Like David M above, my team is completely baffled by the idea that date of birth and phone number are somehow less private than email -- and standard auth identity (email) is NOT supported.

Weighing in here in the hopes that LinkedIn wakes up to the industry standard.

Jeremy Johnstone's picture
Joined: 2011-04-17
Apr 19, 2012

Hi Jackson,

There is no industry standard that an email address is a GUID for a user. Sure, it's an identifier, but it's not a GUID in any respect. Yes, we understand the desire not to put <input type="text" name="email"> on your page (and the associated basic backend work to store / validate that), but it's not part of our current API offering at this time. When this changes, believe me, I will be the first to post and let you all know.

-Jeremy

Brentan Alexander's picture
Joined: 2011-06-01
Apr 26, 2012

No need to get defensive here...we know "its not part of [the] current API offering", hence this thread asking for it. People keep posting as its clearly something a lot of people want...and I am now posting to add my voice to that crowd as well. Ill take the wording of "at this time...when this changes" as a sign of hope that you hear us and are adding the change to your roadmap...

All I am left with from this whole discussion is the feeling that LinkedIn is only concerned about user experience on its own website. This restriction creates a worse user experience on all of our sites as we have to essentially have the user auth with linkedin, and then present them with a 'o by the way we need you to enter your email address' screen to get all the info we need (which is unnecessary for our 'login with facebook' button). If linkedin actually wants external developers to build products and services around its API, it should consider the user experience throughout the entire linkedin ecosystem, not just on its own website. Even a proxy email at a linkedin domain that forwards to the user would be better than what we get now (nothing)...and as many have mentioned, I find it funny that a user can auth with linkedin and I get their phone number but not their email.

Jeremy Johnstone's picture
Joined: 2011-04-17
Apr 26, 2012

Hi Brentan,

My apologies if you felt I was being defensive, not my position at all. :)

As to the second part of the first paragraph, we in developer relations have "heard" you since day one. Even the product management team has clearly heard the message. The issue is it's not just a "flip this on" type thing and needs a proper implementation which addresses all the concerned party's requirements, not just the ones of the developer community. This takes time.

I do feel your second paragraph is a bit inaccurate, but you definitely are correct in that the highest priority of LinkedIn is our members. Developers might not like the fact they play second fiddle to the members, but it's a fact of life and isn't going to change anytime soon. I would be just as frustrated if I were in your shoes, I know you are just trying to solve a problem yourself. That said, if you step back, you can also see that we are doing the right thing for our members based on the current architecture / permission structure.

As to all the comments about this or that field (like phone number, DOB, marital status, address, etc) being available in the API, but not email address, they all fall into the following buckets:

1) Are publicly exposed on the profile already (email is not)
2) Have visibility restrictions which the member can configure (aka DOB, marital status, etc)

-Jeremy

Dominic Tancredi's picture
Joined: 2012-05-01
May 1, 2012

Fascinating read. Here's my assessment:

- based on Linked In's data model of "Multiple e-mail addresses" associated with an account, adding the "email" field to the API would require a list of e-mails
- they would need to identify which e-mail is the "primary" most likely (otherwise, everyone would complain they wouldn't know which e-mail to use for 2 years)
- they would need to add a "granular permissions" model to the API to be able to request permissions for "user-email" access. Difficult to graft on to an existing API. This is Facebook's API pattern for requesting data, where you have a step of explicitly requesting, and granting specific groups of user data
- as @Brentan suggested, they could add a "proxy" e-mail to EVERY user account that could be used as an association (this was an early Facebook API solution, until they solved their granular permissions issue of explicitly requesting and granting the user e-mail field). Not to mention FB put a "spam review" to flag spam messages used throughout this system, and eventually migrated away from it once their permissions development was finished.The cost of adding a "proxy" e-mail to be forwarded for each of the 122MM members, both in creating that association, testing, and deploying to the data-set would make the "proxy" feature that would EVENTUALLY BE DISCARDED is almost logically unviable. Better to invest in the time and effort to solve the permissions model coupled with the multi-e-mail association per user.
- Once granular-permissions is solved on the API-end, it has to be implemented and disseminated as well to the User's settings (which it may already be)... per e-mail for using publicly / privately (i.e. please allow my linked-in@something.com e-mail to be public, but none of my other e-mails). Tack on the UX/UI to make that, testing, etc. and count the hours.
- Another key argument is "it's in the product plan; we're just busy". Looking at the business requirements above (solving granular permissions business logic (which is a whole development track on its own), implementing and testing on the front-end, adjusting the API to retrieve and display emails and "primary", adjusting the data model for "primary", adding a magnifying glass of "spam" protection (business e-mail address are a bit more valuable than consumer-related ones for certain business-practices, if you consider being able to pull a data-set that includes "titles / professions", and e-mail only "Presidents, Owners, and CEO"'s of companies to offer your services vs... regular consumer? Facebook DOESN'T list user's title / years of business / occupation (reliably).
- Anyone find a "Linked In API Roadmap"? Just a thread from 2010 (https://developer.linkedin.com/thread/2074). I love the "Adding a Roadmap is on our Roadmap". It's all right to not publish it (and forgive me for making the comparison but it's flattering to be compared) but FB has a developer roadmap, so it was easier to see how swamped with features, development, effort, etc.

All of these issues mean
a) the feature requires a large amount of development to solve a multiple-faceted problem (permissions, data models, ux-ui, spam-protection, etc.)
b) it exposes risk of spamming to their users (yes yes they "grant" permission for whatever 3rd party to have access to the system but one-click login/profile creation oAuth is becoming accepted standard without User's knowing the risk, and it takes just one bad apple to ruin a user's experience),

As suggested, the issue could be solved on the 3rd party end by adding a 2nd step e-mail-and-verification field on account creation; this is an industry-wide standard and most likely already implemented by user's wanting to integrate Linked In's oAuth... which of course everyone says "what's the point of integrating a step if we already do it"? But everyone is complaining about Account CREATION and not Account Linking. An already logged-in user, authenticated, with e-mail, could link their Linked In account and have access to that very-rich data-set. The real complaint is Account Creation / e-mail address pre-verified via Linked In. Tough, but the problem-set is so large, the development resources required to architect and implement so costly, and the visibility on Linked In's Roadmap so dim, that until there's an announcement on some Linked In Dev Channel (which is probably on the Roadmap) I can't imagine this issue being solved any time soon.

I can sympathize with the Linked In Dev Team (great job on the Client-Side Templates assessment by the way!), and suggest at least making a Development Roadmap available (::cough http://developers.facebook.com/roadmap/ ::cough).

Jeremy Johnstone's picture
Joined: 2011-04-17
May 1, 2012

Hi Dominic,

Thank you so much for the very thoughtful and detailed post!! It's nice to see someone actually speaking up and identifying the (probable) issues at hand and not trivializing the problem into "it's just adding another field, should take you two seconds, right?".

I've been advocating internally for a public roadmap since I joined a year ago, but unfortunately it's not been acted on yet for various reasons. My hope is that it will happen at some point, but as we aren't permitted to even comment on unreleased functionality / estimated timelines, I don't foresee a detailed roadmap coming any time soon.

-Jeremy

Neil Munro's picture
Joined: 2011-10-03
May 2, 2012

To me this is related to the wider issue of 'relationships management' which has given me headaches both as a user (who is continually asked for access to my contacts) and as a developer (who has little choice but to ask for these contacts!).

So I have set up a group to discuss ideas to try and come up with a solution for this. I have a rough idea for one option that I have provisionally called Open Relationship Protocol :-J Please feel free to join and comment: https://groups.google.com/forum/?fromgroups#!forum/open-relationship-protocol

Dominic Tancredi's picture
Joined: 2012-03-20
May 7, 2012

Hi Jeremy,

It's not an easy issue, and should be recognized as such. It's a shame about the RoadMap, but given Linked In is a publicly traded IPO, releasing what the future development tracks are becomes... something that needs to be run by marketing I suppose. Sad but true.

Gopakumar K's picture
Joined: 2012-04-22
May 17, 2012

Hi Kirsten Jones,

There are 2 version of profile.
1. standard
2. Public

Is there is any difference between these two. If i use "Standard" would i get the email id from linked in.?

OR

Is there is any API Needs to purchase from linkedin to get the emial id ?
Please replay ASAP

Gopakumar K's picture
Joined: 2012-04-22
May 17, 2012

I am also facing the same issue . Please any one help me

Peeyoosh Kumar's picture
Joined: 2012-05-14
Jun 2, 2012

Yes, we can do it but what if that user entered your E-mail id instead of his? then he'll get a verified account with your email id.

Vivekanand Soundalage's picture
Joined: 2012-06-07
Jun 7, 2012

you are right bro

Satyaswarup Satpathy's picture
Joined: 2012-03-15
Jun 18, 2012

Hi All,
I saw www.live.com is able to extract email addresses of my connections from linked in account. Can anybody able to tell me how it is possible for them but not for my website.

Thanks,
Satya

Satyaswarup Satpathy's picture
Joined: 2012-03-15
Jun 18, 2012

Hi Kirsten/Jeremy,

www.live.com is also using oauth process to extract email address from linkedin account. I am wondering how they are getting this information from linkedin as it is not a supported field.

Thanks,
Satya

Alfred Obereder's picture
Joined: 2012-03-01
Jun 21, 2012

Just to add my two cents... the missing email field is causing my project much headache as well :(

Satyaswarup Satpathy's picture
Joined: 2012-03-15
Jun 22, 2012

Hi Alfred,

I am unable to fetch email address from linked in as it is not a supported field. But i found Microsoft live website is able to fetch my connection's email address from linked in. So only Kirsten/Jeremy will able to answer this question how it is possible for Live to fetch as they are not disclosing email.

Thanks,
Satya

Joined: 2011-02-13
Jun 23, 2012

Like you, I am a 3rd party developer and I would love to get the email address(es) of the user as well from the Open API, but it's currently not available via this program. Partners such as Microsoft have signed agreements with LinkedIn and have a different access level then us using the Open API. It can be frustrating when you see another 3rd party application with the exact same access as you want but that functionality is not part of the current (or ever will be in some cases) Open API program. Unless you are able to get a response to the "request for additional access form" from the business development group, you're out of luck.

For example, I'm hoping that Inbox / Accept Invitation access is added to the Open Program at some point (soon). That is more likely than adding email as LinkedIn has stated time and time again that the user's email address is a guarded element of the profile that they don't want used to send the user SPAM by a 3rd party developer. As a LinkedIn user I can certainly appreciate that.

Corey Grusden's picture
Joined: 2012-06-25
Jun 26, 2012

Ah, just ripped out LinkedIn authentication for my application.

Regardless if LinkedIn is different than Facebook and GitHub does something different than both, the point remains.. I'm not going to introduce having someone enter their email address to authenticate with LinkedIn on my side. They can just go ahead and add a username and be done with it.

I fear how many applications out there are just checking the first name and last name of the user from LinkedIn and then pulling up a user and attaching their LinkedIn token to that. Means most sites that I've logged in to with LinkedIn can probably change their name to Corey Grusden as well if that's all their checking and log in as me.

Joined: 2012-06-25
Jun 26, 2012

Hi Kirsten
I just had a question on the same lines. I have an email address of a college in linkedin (but, he is not a connected member to me).
I am able to send him mail by logging in to linkedin using the inMail feature(with premium privileges). But, I didn't find any API for the inMail feature. Is there an API for inMail feature ? Please clarify.
I did checked the documentation multiple times and found that it provides API's for Invitation and messaging. But, I don't find the API for inMail even when i have the linkedin mailid of my person.

Kindly, reply.

Thanks
Sathya

Alex Novikov's picture
Joined: 2012-06-05
Jun 27, 2012

To LinkedIn Stuff:

If it is such a big issue to provide user's emails to the applications,
why don't you guys (at least temporally ) provide email in form of LinkedInUserID_random_salt@linkedin.com
and setup a pop3 server to forward such emails to the actual user email?
salt could be 9 letters to prevent spammers from figuring it out.
you can even add APP ID into this generated email so it could be something like UserID_AppID_blabla@linkedin.com

this way, before forwarding you can validate app status and if application is blocked (by you) you will not forward this emails.

both user and 1 level of his connections should have such emails avaliable via API.

This way developers can use existing facilities for normal mail notification, identification ect and this email will remain the same

(random salt should be generated once per user and remain constant)

is this satisfy your security/privacy approach ?

thanks.

Joined: 2012-07-02
Jul 2, 2012

Hi,
I am working on LinkedIn people search API, and able to search people within the network of ACTIVE LOGGED IN USER.
My API call url is http://api.linkedin.com/v1/people-search:(people:(id,first-name,last-name,api-standard-profile-request,site-standard-profile-request,headline),num-results)?title=software&count=10 and it is working good.
Does anyone help me out how to search people regardless of the network of ACTIVE LOGGED IN USER.
For example, I am ACTIVE LOGGED IN USER and I want to search people having title=Software&company-name=Google, but I am NOT ASSOCIATE WITH GOOGLE IN ANY OF THE WAY(CONNECTIONS , NETWORKS FOLLOWING, FOLLOWER ETC.)
API call would be similar to "http://api.linkedin.com/v1/people-search:(people:(id,first-name,last-name,api-standard-profile-request,site-standard-profile-request,headline),num-results)?title=Software&company-name=Google=10".

Thanks & any help would be greatly appreciated.

Joined: 2012-06-11
Jul 8, 2012

To Kirsten and the LinkedIn staff:

- To publish maiden name and full birthdate via the API, but not the email address, is absurd.
- This likely reflects some other unstated motivation on LinkedIn's part, as the reasons stated above are flimsy and hollow
- All the other major login APIs publish the email address of the user (FB, G+, Github, etc)
- In addition, there are literally dozens of other social-login options out there to choose from

Bottom line:
Sorry I wasted my time on LinkedIn login, I'll just use several of the other available ones that do publish email - with Mozilla Persona/BrowserID being the cleanest and most private.

j

Kamyar Mohager's picture
LinkedIn Employee
Joined: 2012-04-04
Jul 9, 2012

Hi all,

We do listen to our developer community, particularly when it comes to possible feature requests. While we can't comment on what we're building out specifically in our platform, rest assured these threads don't go unnoticed so please be patient with us. Once something becomes official our team will definitely make sure our blog and documentation reflects the new changes.

Thanks,
Kamyar

Ben Wilks's picture
Joined: 2011-10-21
Jul 31, 2012

Hi,

I have read most of this post but may have missed this point, so apologies if it has been answered, we are creating a web and mobile app that will hopefully become widely used (obviously!). My issue is that whilst researching competitors it is clear that they have access to linkedin email addresses of not only the user but also the users contacts, this is not available via the open API and when i requested information I was told that no 3rd party apps had this access, this is categorically untrue. Could someone from LinkedIn let me know why someone would not answer the request truthfully and also without being Microsoft or other how one might ever get this access? It seems unfair to only allow larger corporations access to this rather than those that are trying to disrupt those same organisations? Is it a matter of monies paid?

Many thanks in advance
Ben

Manickam Ravi's picture
Joined: 2012-04-14
Aug 3, 2012

Hi all,
Many social network are providing email.id but cont get in linked in.what problem will come only for linked in? give any idea to get email id

Thanks

manickam

Nick Kusters's picture
Joined: 2011-09-28
Aug 3, 2012

Hey Ben,

Linked In provides e-mail addresses to 3rd parties via their non-public API. It's not possible to access it with the public API.

From what I've gathered, it's extremely hard to get access to the non-public API (most will never even get an e-mail response).

So good luck :)

Ben Wilks's picture
Joined: 2011-10-21
Aug 3, 2012

Hi Nick,

Many thanks for your response, no surprise that LinkedIn didn't respond!

I have found a number of apps that can get emails out of LinkedIn and some of them are not what i would consider 'safe', so the thought of my details being all over the web thanks to LinkedIn giving certain partners access actually makes me want to cancel my LinkedIn account.

Thanks again, I'll let you know if i get a reply from the black hole of LinkedIn non-public API!!

Cheers
Ben

Kamyar Mohager's picture
LinkedIn Employee
Joined: 2012-04-04
Aug 3, 2012

Ben, we've replied to this thread many times in the past :)

As it stands at this very moment, emails aren't exposed via the API. But I assure you that if and when email is exposed we'll make an announcement/update our documentation/let our developers know. There are business reasons as to why some fields are exposed and others aren't. I can't comment to those reasons but LinkedIn is aware of how this is important to our developers so trust me, it doesn't go unnoticed.

Ben Wilks's picture
Joined: 2011-10-21
Aug 6, 2012

Kamyar, you miss my point, i was enquiring as to why the email IS exposed via a different API to people like Microsoft, is it possible for smaller companies to partner with LinkedIn to get the same information and play on a level playing field with the big boys? How can one be expected to create a disruptive product if the information available isn't the same for everyone? Is it a matter of money? Or company size?
Ben

Kamyar Mohager's picture
LinkedIn Employee
Joined: 2012-04-04
Aug 7, 2012

We're excited to announce that we've revamped our member permissions to also include email! This blog posts goes into detail about some of our new updates, including email support: https://developer.linkedin.com/blog/making-it-easier-you-develop-linkedin

Looking forward to seeing some great apps developed with these new enhancements.

Paul Aicher's picture
Joined: 2012-06-26
Aug 8, 2012

thanks for updating us on this status. Are the changes currently in play? I am trying to get email and it isn't coming across for the 1st level connections?

https://api.linkedin.com/uas/oauth/requestToken?scope=r_basicprofile+r_emailaddress

http://api.linkedin.com/v1/people/~/connections:(id,first-name,last-name,formatted-name,phone-numbers,main-address,picture-url,public-profile-url,three-current-positions,email-address,api-standard-profile-request:(url))

I get everything else but there is not an email-address tag in the response. Am I missing something?

Ryan Shillington's picture
Joined: 2012-02-26
Aug 9, 2012

I'm having the same problem Paul. I'd love to stop asking my users for their LinkedIn email.

When I request: http://api.linkedin.com/v1/people/~/email-address (as mentioned in the blog post)

I get:

{
"errorCode": 0,
"message": "Unknown field {email-address)} in resource {Person}",
"requestId": "94UUZTKZUX",
"status": 400,
"timestamp": 1344520107789
}

Also, I've noticed that regardless of the scope that I set (even r_fullprofile), the LinkedIn page that asks if it's okay to auth my site hasn't changed. You'd think it would say something like "They want everything! Are you sure?"

Do I have to apply somewhere to make this work?

EDIT: I see we're not alone. New thread started here: https://developer.linkedin.com/forum/can-we-get-email-address

SOLVED: You need to add a new account (and get a new key). Then it all works. They're working on migration.

Kamyar Mohager's picture
LinkedIn Employee
Joined: 2012-04-04
Aug 9, 2012

Hey guys, we're working on a migration plan for existing applications. The new member permissions only apply to newly registered applications.

Thanks!
Kamyar

Pages