3 ms·
Great that they are moving to a more open approach finally allowing _all_ developers access to their API. However it's not as good as it seems: 1. There is no
by spif 17y ago
Great that they are moving to a more open approach finally allowing _all_ developers access to their API.
However it's not as good as it seems:
1. There is no support for contact details like phone-number, email etc.
2. The API is read-only, and that sort of beats the purpose of this API.
(At least judging from the limited documentation available at the moment.)
- pie 17y agoWow, this API has been a long time coming. It looks to me like there are write operations for status, activity stream, friend invitations, and direct messaging. I'm not too surprised that LinkedIn does not offer all the contact details. Phew. This documentation is organized in a somewhat annoying fashion.
- spif 17y agoYeah I'm not surprised either about the contact details, however if you are authenticating all users via oAuth that should negate the risk for a big part. Imaging Google not allowing you to see the email address via their ContactsAPI, that wouldn't make sense...
- sgoraya 17y agoI agree. Too little, too late. From my experience, linkedin has lost a bit of steam over the last 6 months or so. I used to check the site regularly, update contacts, join discussions, etc. but have not done so lately. I was initially excited by the first release of API but was disappointed after digging into it a bit. Having to apply etc. just killed it for me (I eventually got accepted but by that point had no interest). This release is more of the same and is rather limited as spif points out.