Comments on: The LinkedIn API Opportunity http://blog.linkedin.com/2007/06/26/the-linkedin-1/ The corporate blog of LinkedIn, the world's largest professional networking site. Sat, 12 Dec 2009 02:37:13 +0000 http://wordpress.com/ hourly 1 By: News Digest: Google, Idea, Vodafone, LinkedIn, CarWale, Rediff & More | MediaNama http://blog.linkedin.com/2007/06/26/the-linkedin-1/#comment-13388 News Digest: Google, Idea, Vodafone, LinkedIn, CarWale, Rediff & More | MediaNama Tue, 24 Nov 2009 13:05:10 +0000 http://wptheme.site/?p=276#comment-13388 [...] has announced that it will be opening up its APIs for developers so that applications can be built around it. [...] [...] has announced that it will be opening up its APIs for developers so that applications can be built around it. [...]

]]> By: LinkedIn’s Obsession with Guarding its User Data will Alienate its User Base at Media Transparent http://blog.linkedin.com/2007/06/26/the-linkedin-1/#comment-7710 LinkedIn’s Obsession with Guarding its User Data will Alienate its User Base at Media Transparent Thu, 26 Mar 2009 01:41:42 +0000 http://wptheme.site/?p=276#comment-7710 [...] was never very transparent. Although they offered up a LinkedIn API to developers in June, 2007, I can’t name one developer-based LinkedIn API built application (I can name partners like NY [...] [...] was never very transparent. Although they offered up a LinkedIn API to developers in June, 2007, I can’t name one developer-based LinkedIn API built application (I can name partners like NY [...]

]]> By: Charlie Crystle http://blog.linkedin.com/2007/06/26/the-linkedin-1/#comment-404 Charlie Crystle Fri, 01 Aug 2008 20:38:57 +0000 http://wptheme.site/?p=276#comment-404 We're excited to see the API. I think preannouncing the public API and keeping it private, well, that makes everyone cranky and impatient. We'd love to integrate. It's hard to know what we want and what we need until we see what you have chosen to expose and not expose. But for starters, I'd say any data public to a profile and public functions. We’re excited to see the API. I think preannouncing the public API and keeping it private, well, that makes everyone cranky and impatient. We’d love to integrate. It’s hard to know what we want and what we need until we see what you have chosen to expose and not expose.

But for starters, I’d say any data public to a profile and public functions.

]]> By: Lucian Beebe http://blog.linkedin.com/2007/06/26/the-linkedin-1/#comment-403 Lucian Beebe Thu, 26 Jun 2008 05:51:42 +0000 http://wptheme.site/?p=276#comment-403 I appreciate all the inquiries about the APIs both in email and in the comments on the blog. I think it may help to describe where we are and what we are building to address the statements asking about when we will be public and why we aren't today. The short answer: we aren't a public program because we're still in a beta phase. The longer answer: In our case, "beta" has more of the traditional meaning. We are testing a platform of APIs that allows many use cases. We are experimenting with a wide variety of use cases: job sites such as Apec and SimplyHired; business news sites such as CIO.com and BusinessWeek; toolbar and desktop applications such as Xobni; events registration and management applications; various forms of enterprise software, and many more. And there are several use cases we are not testing with partners just yet. We don't think we have the right platform to support CRM integrations, for example. Based on the experiences we gain from the beta period, we'll decide how to proceed. Quite honestly, we may remain "private" in that we will evaluate all partners to work with. We'd all like to see a public program, but our experiences during this beta period will guide us in making that decision. One key requirement that the beta period has underscored is privacy. We have a fundamental requirement to abide by our privacy policy both in letter and in spirit. We must be sure that the people we work with will treat your privacy the same way we do. If we do a public program and have no interview process before granting access, then we must have the platform built such that we have high confidence that privacy policies will be respected and a very fast control valve if there is any question. So, <del datetime="00">send an email to developers@linkedin.com</del> submit your API access requests <a href="http://www.linkedin.com/static?key=developers_apis" rel="nofollow">here</a>. The web form for applications request can be found <a href="http://www.linkedin.com/static?key=developers_opensocial" rel="nofollow">here</a>. We are running a few day's delay in getting back to people, but we are answering all requests. When you do send a message, include answers to four key questions: • What do you want to do with the LinkedIn APIs? • Where will this integration appear? • What data do you need from us? • What will you do with the data we provide to you? I hope this helps describe where we are. For those of you who think the only API program is a public API program, I hope this isn't too disappointing. But don't give up simply because we are interviewing partners: if you have a good idea, we want to support you, so don't hesitate to let us know: <del datetime="00">developers@linkedin.com</del>. Lucian I appreciate all the inquiries about the APIs both in email and in the comments on the blog. I think it may help to describe where we are and what we are building to address the statements asking about when we will be public and why we aren’t today.

The short answer: we aren’t a public program because we’re still in a beta phase.

The longer answer: In our case, “beta” has more of the traditional meaning. We are testing a platform of APIs that allows many use cases. We are experimenting with a wide variety of use cases: job sites such as Apec and SimplyHired; business news sites such as CIO.com and BusinessWeek; toolbar and desktop applications such as Xobni; events registration and management applications; various forms of enterprise software, and many more. And there are several use cases we are not testing with partners just yet. We don’t think we have the right platform to support CRM integrations, for example. Based on the experiences we gain from the beta period, we’ll decide how to proceed.

Quite honestly, we may remain “private” in that we will evaluate all partners to work with. We’d all like to see a public program, but our experiences during this beta period will guide us in making that decision.

One key requirement that the beta period has underscored is privacy. We have a fundamental requirement to abide by our privacy policy both in letter and in spirit. We must be sure that the people we work with will treat your privacy the same way we do. If we do a public program and have no interview process before granting access, then we must have the platform built such that we have high confidence that privacy policies will be respected and a very fast control valve if there is any question.

So, send an email to developers@linkedin.com submit your API access requests here. The web form for applications request can be found here. We are running a few day’s delay in getting back to people, but we are answering all requests. When you do send a message, include answers to four key questions:

• What do you want to do with the LinkedIn APIs?
• Where will this integration appear?
• What data do you need from us?
• What will you do with the data we provide to you?

I hope this helps describe where we are. For those of you who think the only API program is a public API program, I hope this isn’t too disappointing. But don’t give up simply because we are interviewing partners: if you have a good idea, we want to support you, so don’t hesitate to let us know: developers@linkedin.com.

Lucian

]]> By: Andrew http://blog.linkedin.com/2007/06/26/the-linkedin-1/#comment-402 Andrew Thu, 26 Jun 2008 01:48:01 +0000 http://wptheme.site/?p=276#comment-402 It's pretty annoying that the API's are being selectively released - we're now seeing various companies come up with applications that integrate with LinkedIn and they are getting a competitive advantage because the API's aren't available to everyone. You really should treat your developer community equally. If the API's are sufficiently complete for Xobni to build applications around them, then why can't other companies build applications around them? It’s pretty annoying that the API’s are being selectively released – we’re now seeing various companies come up with applications that integrate with LinkedIn and they are getting a competitive advantage because the API’s aren’t available to everyone.

You really should treat your developer community equally.

If the API’s are sufficiently complete for Xobni to build applications around them, then why can’t other companies build applications around them?

]]> By: David Vandervort http://blog.linkedin.com/2007/06/26/the-linkedin-1/#comment-401 David Vandervort Fri, 30 May 2008 14:12:54 +0000 http://wptheme.site/?p=276#comment-401 I'm confused. You have specific apis for specific sites? That's not how an API works. Is there any plan to release a public API that any old programmer can grab and use? I am currently working on a project that might find that useful, but not if we have to jump through hoops to become some special "partner." I’m confused. You have specific apis for specific sites? That’s not how an API works. Is there any plan to release a public API that any old programmer can grab and use?

I am currently working on a project that might find that useful, but not if we have to jump through hoops to become some special “partner.”

]]> By: Sumit Saxena http://blog.linkedin.com/2007/06/26/the-linkedin-1/#comment-400 Sumit Saxena Thu, 15 May 2008 05:04:28 +0000 http://wptheme.site/?p=276#comment-400 Hey, do we can have access of the APIs? Hey, do we can have access of the APIs?

]]> By: Mario Sundar http://blog.linkedin.com/2007/06/26/the-linkedin-1/#comment-399 Mario Sundar Mon, 05 May 2008 19:09:29 +0000 http://wptheme.site/?p=276#comment-399 To everyone asking about API release date, We've released APIs which have resulted in BusinessWeek, SimplyHired and APEC integrations thus far. Please continue emailing developers@linkedin.com. Stay tuned to the blog for latest news. Thanks for your patience, guys. To everyone asking about API release date,
We’ve released APIs which have resulted in BusinessWeek, SimplyHired and APEC integrations thus far.

Please continue emailing developers@linkedin.com.

Stay tuned to the blog for latest news. Thanks for your patience, guys.

]]> By: martin english http://blog.linkedin.com/2007/06/26/the-linkedin-1/#comment-398 martin english Fri, 02 May 2008 02:59:04 +0000 http://wptheme.site/?p=276#comment-398 Hey it's our own kind of first post (of the month) asking if / when the API will be released ? Hey it’s our own kind of first post (of the month) asking if / when the API will be released ?

]]> By: Erik Bower http://blog.linkedin.com/2007/06/26/the-linkedin-1/#comment-397 Erik Bower Thu, 24 Apr 2008 19:09:23 +0000 http://wptheme.site/?p=276#comment-397 Where is the API documentation? I can't find it anywhere. Where is the API documentation? I can’t find it anywhere.

]]>