Below you find the resources available for the LinkedIn API, as well as some basic description for each one of them.
- Network Updates
In this architecture, every resource is access via an HTTP GET request. The Profile resource provides all the information that is available for a user, based on selectors (user id or profile url). In order to get further information about a user’s network (connections, activity, etc.), Connections resource provides you with details regarding user’s connection. Searching through the LinkedIn network is achieved using the Search resource, which matches the criteria provided. Messaging resource allows users to send and receive private messages, as well as invitations to connect. Please note that, Messaging requires HTTP POST requests rather than GET. To post updates, receive updates, get comments and/or likes, you have to use the Network resource. Every HTTP request (either POST or GET), returns an XML with the appropriate data requested.
Search for people with keywords anargyros akrivos:
HTTP GET http://api.linkedin.com/v1/people-search?keywords=[anargyros akrivos]
Get profile information for user akrivos:
HTTP GET http://api.linkedin.com/v1/people/id=akrivos
Get akrivos‘ connections:
HTTP GET http://api.linkedin.com/v1/people/id=akrivos/connections
Getting updates for Vanessa Hughes
HTTP GET http://api.linkedin.com/v1/people/id=QpK8ApA59n/network/updates?scope=self
<updates total="250" start="0" count="10">
<headline>Certified eBay Trading Asst & Power/TOP Seller of ANTIQUE WESTERN ITEMS</headline>
<current-status>I new I had a good plan & then I get this...Seller Special: 50% OFF SALE2 days only! Feb 9-10 #Ebay</current-status>
Issues to bear in mind
The basic issue is that many LinkedIn API calls require that the user is authenticated, making user authorisation a necessary evil, before making any call to the API.