Five weeks ago I blogged about LinkedIn’s API policy, and I also applied to develop an application with their API. I had no illusion that my idea was earth-shattering, but I thought it was a good one, and one that LinkedIn might even be able to monetize. It was no iFart, that’s for sure (meaning it’s not a simple but highly appealing app that people inexplicably want) So, what was LinkedIn’s reponse?
So far, absolutely nothing. No acknowledgment of my submission, and no answer positive or negative.
Seems like further evidence to Tangyslice’s critque of LinkedIn as being not quite connected enough. How likely is it that they’re so swamped with requests that they can’t even send me a “thanks but no thanks”? Is five weeks too soon to wonder? Is their form busted? Did they fire the guy in charge of reveiwing these apps? Could they be arrogant enough to think it’s not worth responding?
Perhaps it’s a cold calculation that if they sent me a rejection letter, I would post it to the blog and mock them for it. I suppose they’d be right on that one.
I’ll submit again just to make sure there wasn’t a technical glitch, but I’m not feeling too bullish on LinkedIn apps right now. Has anybody out there had more success in being accepted or even rejected by LinkedIn’s API Decider?
I have a friend that works at LinkedIn in their tech group. His name is Andrew S*****. Shoot him an email ( email@example.com ) … he might be able to help.
What part of this do you not understand?
“How to develop for the Platform
“The LinkedIn application platform is not publicly available for all developers. We evaluate requests to develop for the LinkedIn platform from partners who have clearly compelling value to our users and who can rigorously follow our privacy policies. We are looking for applications that provide clear business utility to LinkedIn users. LinkedIn is not a place for sheep throwing. There is equal opportunity to build applications that apply to all LinkedIn users as there is to develop applications that apply to just a targeted portion of the user base. If you think you qualify and have a compelling user value proposition, let us know using the form below”
Hi Ed. I’ll give you what LinkedIn hasn’t given me, a reply. Thanks for your comment. It’s not really what I had in mind for my blog but I appreciate you taking the time to compose it. I wish you all the best in developing this comment further on other blogs.
Wow, that Ed guy is an assclam. I love when you get cunty responses for just posing questions. What a condescending dildo! Sounds to me like LinkedIn probably has a ‘flat’ management org and no one knows what to do with your response, or their content to be also-rans with wack shit like LinkedIn for the iPhone; which is about as usefull as iPity.
BTW: came to your blog while researching APIs for social networking sites for an idea that I have.
Good luck on any projects you might be into.
I’ve had the same – no response. I finally started adding comments like crazy to their blog(s) about it and eventually got an canned response from one of them stating I’d have to wait like everyone else until some public API is available (this was well over a year or more ago). I guess my app idea was not high profile enough for them (which was to build integration into some well known CRM applications). It seems like they are only approving the apps that best serve them, not their users and certainly not 3rd party developers.
I am not holding my breath for a public API. IMO, their lack of a real, public API will be the cause of their ultimate death.
Quite likely the reason you don’t get a reply is because legally a reply could be construed as acknowledgement of your idea by representatives of the company, and that could potentially be used in legal action down the road if they did end up using your idea (or anything similar). If they don’t acknowledge it (which is standard company policy for the most part), then they don’t open up that can of worms. Also, the legal precedence is that if you offer unsolicited “ideas” that are not protected by patents, then those ideas become property of the company you offered them to.
> I am not holding my breath for a public API.
now it’s about time to hold it…