Tell HN: LinkedIn's API will be restricted next week
One of the major restrictions is limiting the access of the r_fullprofile fields to only explicit LinkedIn partners. This is used by a lot of startups to create a great onboarding UX and minimize user data entry.
While this is a disruption to developers who will now have to adapt their onboarding, more importantly, it's a major setback for millions of LinkedIn users. LinkedIn is heightening their walls and there will no longer be an easy way for LinkedIn users to export their profile data out of LinkedIn and use it for other purposes.
We build an online resume/portfolio creation tool and are offering all our premium plans for free when users signup with LinkedIn until our API access to LinkedIn profiles gets turned off on May 12: https://www.visualcv.com/?ref=freeLinkedIn
Before the LinkedIn API grace period ends, we would love to hear from any more startups that are currently relying on the LinkedIn API for signups and are offering a promo to their services one last time. Please list your startup in the comments below.
44 comments
[ 3.5 ms ] story [ 89.8 ms ] threadExposes a few methods. Main use case was just to traverse linkedin results.
Contributors welcome!!!
I completely ignore my timeline and I only connect with people I've met. LinkedIn's been helpful when I find a potential donor (or someone else I want to talk to) and I can see who's connected with them. If I have a 2nd degree connection with them, then I begin my research to actually see the best way to get in touch with them. Far too many people connect with people they don't know for LinkedIn alone to be a useful tool.
Follow that rule and you won't need to worry.
Name one product that doesn't rely on another product.
That said, I think that: "don't make your service depend on other services without some sort of contract or agreement to provide" is a better rule of thumb than the one above.
Basing your product on top of LinkedIn? The core of their business isn't anywhere near providing that API.
Building your company around the core business of LinkedIn/Facebook/etc is dumb, because you are nothing more than a complement to their core mission. Best case, you become a commodity and achieve modest success, but the oxygen gets cut off at any time.. If you're very successful, you become a feature of the mother product.
When you're Apple buying memory from Samsung, that's different. Samsung's output is memory chips... that's the business. If nobody buys memory chips, they lose money.
Developing for the open web and trying to get people to websites in the current mobile/social era is increasingly brutal unless you are willing to be completely dependent on a handful of big companies.
I think what you mean to say is "don't build a product that depends on LinkedIn", and to that, I absolutely agree. LinkedIn, with its chain email spamming and forced mass invites, is literally the post-child for internet dark patterns and unethical behavior. Furthermore, the sheer volume of people on there automatically force recruiting agencies to use bots (or at least copy-and-paste) to spam folks on there, and in general leads to bad returns for the recruiter and tons of spam for you the programmer.
Unless you have an ironclad contract with whomever you are partnering with(whose API you are using) and know exactly what you get from them and they get from you and for how long, you should not be depending on them.
If you want to spend a few weekends writing to some API and don’t care if the rug gets pulled out from under it, and all your users then fine. If you want to support an API in a product that will survive without that integration that is also fine. Just don’t gamble your entire product and your future user base on API's that can disappear overnight when some dickhead MBA decides he isn’t making his numbers and the free loader third parties aren’t worth it any more.
But to your point, LinkedIn's practices can be a little pushy, but the site still provides decent value to me (it got me my current job). I can put up with ignoring mass invite requests, recruiter messages, and configuring my notification settings to maintain this professional network. It may get me my next job in 5 years, so for me it's totally worth it.
Maddeningly, at least one dictionary disagrees: http://www.merriam-webster.com/dictionary/literally (2)
These corporations assume they can do it all on their own, as they have billions of dollars and great engineers.
Still, it's quite useless: greed is what really drives true innovation.
Good luck Linkedin
If something like this is driven by lawyers, that's ridiculous: they advise, not prescribe.They are tools, not the brain manipulating the tool.
Investors .. maybe. But, why would investors be so myopic? Or rather, do such myopic investors have enough control to push this?
To me it sounds like linkedin leadership saw how much they were making from recruitment and decided to open up the sales side of the business too. And, instead of competing for sales data enrichment, they decided to make it a one-player game.
Whatever. Time to buy linkedin stock, and set a reminder to sell in 1-2 years.
This should be a golden age of software but its increasingly resembling a wasteland. Most software is being herded in to app stores which Apple and Google completely control and dominate, and which has reached a saturation level of app developers.
Interesting companies keep putting out awesome API’s, lure in suckers . . er . . developers, only to crush them after the developer has sunk a bunch of time and and money developing for them and about the time the company has developed enough momementum that they don’t need third party developers unless they are fully monetized partners.
And then of course there are the patent trolls.
I had thought to use LinkedIn as one of a few APIs to learn from and to prompt thinking.
Anyone recommend a few good API-backed sites to learn from? Is HN's API particularly good, or simple, or something?
Anything else?
Ex: https://www.reddit.com/r/programming.json
Why yes, that is beautiful. :)
For us LinkedIn integration was obviously critical. We think we can still go forward with what API's are available but we knew full well we were building a business on top of another business's API. So it is what it is. Can't really say it's unfair, they built the platform. Oh well.
The documentation just mentions the limitation in API endpoints, but I'm a bit worried whether it could make the oauth login fail due to permissions requested that you can no longer use.
https://developer.linkedin.com/docs/fields/basic-profile
Really saddened to see LinkedIn restricting this API access. It won't cause any significant disruption to our platform, but destroys the convenience of using LinkedIn.
Does the OP have an API for taking data out for Virtual CV users?
Yahoo! mail recently launched integration with LinkedIn data, and Salesforce.com and Microsoft Dynamics have integration, but no other CRM is allowed to have access.