Get Network Updates and Statistics API
The Get Network Updates API returns the users network updates, which is the LinkedIn term for the user's feed. This call returns most of what shows up in the middle column of the LinkedIn.com home page, either for the member or the member's connections.
Returns a feed of event items. Each item contains a core set of information, such as when it occured, what type of event took place, and whether you can comment and like the item.
However, the format of the event's information can vary widely from type to type. Information about changing a profile is not similar to the status published by an application. Each event type needs to be parsed differently.
We may perodically add new event types to this feed, or deprecate old ones.
To retrieve the member's updates:
To retrieve the member's first-degree connection updates:
To retrieve updates from 1st degree connections of the authenticated user (privacy restrictions will apply):
|scope||no||self to return member's feed. Omitted to return aggregated network feed.|
|type||no||Any valid Network Update Type from the table below. Types must be in all capital letters. To specify more than one Network Update type, add the type parameter to the resource URL for each type.|
|count||no||# of updates to return, with a maximum of 250|
|start||no||The offset by which to start Network Update pagination|
|after||no||timestamp after which to retrieve updates for (Ex: 1243834824000) note: precision is milliseconds since the epoch|
|before||no||timestamp before which to retrieve updates for (Ex: 1243834824000) note: precision is milliseconds since the epoch|
|show-hidden-members||no||true or false. default is false. Whether to display updates from people the member has chosen to "hide" from their update stream.|
Example Parameter Usage
To return up to 50 Status and Picture Updates, starting with the 50th update of those types:
Network Update Types
See Network Update Types for more information on how each network update type is structured and can be interpreted.
An action that occurred in a partner application either by a connection or by an application itself. The contents of the update will be HTML entity encoded.
|CMPY||Company Follow Updates||
A change to one of the companies the member is following.
These updates cover aspects of connections made on LinkedIn. They cover both the user connecting and the user's connections making connections (second degree connections).
|JOBS||Posted a job||
A connection has posted a job posting on LinkedIn
|JGRP||Joined a group||A connection has joined a group.|
|PICT||Changed a picture||
A connection has updated their profile picture.
|PFOL||People Follow Updates||
The authenticated user or one of their connections has started to follow another member. Currently, only LinkedIn Influencers can be followed
|PRFX||Extended profile update||
A connection has updated their extended profile, personal information such as phone number, IM account, and Twitter handle.
A connection was recommended
A connection has updated their profile. This does not include picture updates, which are covered under PICT type.
The fields updated are returned in the XML. Since the first name, last name, and headline are always returned for each update, if those are the only fields you see, then you can assume that the change was to the headline.
A connection has shared an update or link.
This update type is deprecated in favor of SHAR.
A connection has updated their status.
A connection has commented on or liked another update.
Sample XML Responses
All returns follow a standard pattern with variation in the update details section:
- updates: total number of updates and pagination information in attributes
- update: a specific update
- timestamp: when the event occured, in mili-seconds since Unix epoch time
- update-key: unique identifier for the event, similar to an id
- update-type: kind of event, values listed above
- update-content: information on event, schema varies based on type
- is-commentable, is-likeable, is-liked: whether the event accepts comments and likes, or if the event has been liked. Booleans.
- num-likes: number of members who have liked the event
<updates total="250" start="0" count="10"> <update> <timestamp>1265688025372</timestamp> <update-key>STAT-11737890-270-*1</update-key> <update-type>STAT</update-type> <update-content> <person> <id>QpK8ApA59n</id> <first-name>Vanessa</first-name> <last-name>Hughes</last-name> <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> <picture-url>https://media.linkedin.com/mpr/mprx/0__by8vxfjBizcc5a135g1vpgtv6tBz_a13Le0vjpGEiQboFJPfTuuRge2Ue-enkf0CkYYssC1AxTS</picture-url> <api-standard-profile-request> <url>https://api.linkedin.com/v1/people/QpK8ApA59n:full</url> <headers total="1"> <http-header> <name>x-li-auth-token</name> <value>name:D6nh</value> </http-header> </headers> </api-standard-profile-request> <site-standard-profile-request> <url>https://www.linkedin.com/profile?viewProfile=&key=11737890&authToken=D6nh&authType=name&trk=api*a102812*s1397*</url> </site-standard-profile-request> </person> </update-content> <is-commentable>true</is-commentable> </update>
Network Updates Comments and Likes
Some Network Updates may allow and/or contain comments and or likes. To learn how to retrieve a complete set of comments and likes for a update, or how to add a comment or like, read Commenting On & Reading Comments and Likes in Network Updates.
Creating Network Updates
Read Post Network Update to learn how to create your own network updates.
Information about the member's network, such as how many connections they have one and two degrees away.
Sample XML Response
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <network-stats total="2"> <property key="degree-1-count">123</property> <property key="degree-2-count">13633</property> </network-stats>
- Core Concepts
- Job Posting
- Share and Social Stream
- Libraries and Tools
- LinkedIn Policies
- Integrating your OS X Mavericks Application with LinkedIn