Reading Company Shares

You can use the Company Updates API to read shares for a particular company

Note: Before using this API make sure you understand LinkedIn's OAuth Authentication Model.

Reading Company Updates

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. Each event type needs to be parsed differently.

We may periodically add new event types to this feed, or deprecate old ones. Note that the API returns the latest 50 updates only for event type status-update. If you have updates of other types (such as jobs posting, product-updates etc.) then it can fetch up to 250 updates or updates in the last 20 days whichever comes first.

URL

To retrieve the company's updates:

Filter company updates by event type

By default, a company update will only return you the most recent 10 updates

Parameters

Parameter Required? Possible Values
event-type no Any valid Company Update Type from the table below.
count no Maximum # of updates to return
start no The offset by which to start Network Update pagination

Company Update Types

Update Type Description Source Example
job-posting New job postings on LinkedIn by the specified company. Job is posted via the site or the Jobs Posting API on behalf of the specified company.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
<update>
   <timestamp>1315316675037</timestamp>
   <update­‐type>CMPY</update­‐type>
   <update­‐content>
       <company>
          <id>1337</id>
          <name>LinkedIn</name>
       </company>
       <company‐job­‐update>
          <job>
             <id>1940960</id>
             <company>
                 <id>1337</id>
                 <name>LinkedIn</name>
             </company>
             <position>
                 <title>Sales Account Manager</title>
             </position>
             <site­‐job­‐request>
                <url>http://www.linkedin.com/jobs?viewJob=&amp;jobId=1940960</url>
             </site­‐job­‐request>
             <description>Overview: The Sales Account Manager has two core functions; to work alongside and support an...</description>
             <location-­description>London, United Kingdom</location­‐description>
         </job>
         <action>
            <code>created</code>
         </action>
     </company‐job-­update>
   </update-­content>
</update>
new-hire New employees of the company A user updates their current position with the specified company
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
<update>
   <timestamp>1315338683355</timestamp>
   <update-­type>CMPY</update­‐type>
   <update-­content>
      <company>
         <id>1337</id>
         <name>LinkedIn</name>
      </company>
      <company-­person‐update>
          <person>
              <id>14381178</id>
                  <first-­name>Patrick</first-­name>
                  <last‐name>Smith</last-­name>
                  <headline>Enterprise Relationship Manager at LinkedIn</headline>
                  <picture‐url>http://media.linkedin.com/mpr/mprx/0_gPLYkP6SpokSOnUc0-­vDkA9DYulmpzUc0tA3krFxTW5YiluBAvztoKPlKGAlx-‐sRyKF8wBMg5HkD</picture‐url>
                  <api­‐standard-­profile‐request>
                      <url>http://api.linkedin.com/v1/people/14381178</url>
                      <headers total="1">
                           <http-­header>
                              <name>x­‐li-­auth-‐token</name>
                              <value>name:4gRT</value>
                           </http-­‐header>
                      </headers>
                  </api‐standard‐profile‐request>
                  <site-­standard-­profile‐request>
                        <url>http://www.linkedin.com/profile?viewProfile=&amp;key=14381178&amp;authToken=4gRT&amp;authType=name&amp;trk=api*</url>
                  </site­‐standard-­profile­‐request>
             </person>
             <action>
                <code>joined</code>
             </action>
             <old‐position>
                  <title>Actor</title>
                  <company>
                       <name>IndependentContractor</name>
                  </company>
             </old­‐position>
             <new­‐position>
                  <title>Enterprise Relationship Manager</title>
                  <company>
                       <id>1337</id>
                       <name>LinkedIn</name>
                  </company>
             </new-­‐position>
         </company‐person­‐update>
     </update‐content>
</update>
position-change Current employees of the company who have updated their profile A user updates their current title, or adds a new position for the same company as the previous position
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
<update>
   <timestamp>1315338683355</timestamp>
   <update-­type>CMPY</update­‐type>
   <update-­content>
      <company>
         <id>1337</id>
         <name>LinkedIn</name>
      </company>
      <company-­person‐update>
          <person>
              <id>14381178</id>
                  <first-­name>Patrick</first-­name>
                  <last‐name>Smith</last-­name>
                  <headline>Enterprise Relationship Manager at LinkedIn</headline>
                  <picture‐url>http://media.linkedin.com/mpr/mprx/0_gPLYkP6SpokSOnUc0-­vDkA9DYulmpzUc0tA3krFxTW5YiluBAvztoKPlKGAlx-‐sRyKF8wBMg5HkD</picture‐url>
                  <api­‐standard-­profile‐request>
                      <url>http://api.linkedin.com/v1/people/14381178</url>
                      <headers total="1">
                           <http-­header>
                              <name>x­‐li-­auth-‐token</name>
                              <value>name:4gRT</value>
                           </http-­‐header>
                      </headers>
                  </api‐standard‐profile‐request>
                  <site-­standard-­profile‐request>
                        <url>http://www.linkedin.com/profile?viewProfile=&amp;key=14381178&amp;authToken=4gRT&amp;authType=name&amp;trk=api*</url>
                  </site­‐standard-­profile­‐request>
             </person>
             <action>
                <code>changed-position</code>
             </action>
             <old‐position>
                  <title>Creative Advisor</title>
                  <company>
                       <name>Yahoo!</name>
                       <id>1288</id>
                  </company>
             </old­‐position>
             <new­‐position>
                  <title>Search Account Manager</title>
                  <company>
                       <id>1288</id>
                       <name>Yahoo!</name>
                  </company>
             </new-­position>
         </company‐person­‐update>
     </update‐content>
</update>
profile-change A change is made to the company-profile page A company admin updates the company profile
new-product A product is added to the company products page A company admin creates a new product for the company
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
  <update>
    <timestamp>1342029519566</timestamp>
    <update-key>UNIU-c20296-5628879782381879296-FOLLOW_CMPY</update-key>
    <update-type>CMPY</update-type>
    <update-content>
      <company>
        <id>12345</id>
        <name>test_company</name>
      </company>
      <company-product-update>
        <action>
          <code>created</code>
        </action>
        <event-type>
          <code>new-product</code>
        </event-type>
        <product>
          <id>3700</id>
          <name>test_product</name>
        </product>
      </company-product-update>
    </update-content>
    <is-commentable>true</is-commentable>
    <update-comments total="0" />
    <is-likable>true</is-likable>
    <is-liked>false</is-liked>
    <num-likes>0</num-likes>
  </update>
                                     
status-update An update on the company's status or content shared by the company An admin posts a new status update for the company via the API or website
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
<update>
   <timestamp>1315343580250</timestamp>
   <update-­type>CMPY</update-­type>
   <update­‐content>
      <company>
         <id>1337</id>
         <name>LinkedIn</name>
      </company>
      <company‐status­‐update>
         <share>
            <id>s570040063</id>
            <timestamp>1315343580250</timestamp>
            <visibility>
               <code>anyone</code>
            </visibility>
            <comment>Check out today's Fortune Magazine piece, &quot;Data scientist: The hot new gig in tech,&quot; where LinkedIn's senior VP of products and user experience, Deep Nishar, is quoted.</comment>
            <content>
               <submitted‐url>http://tech.fortune.cnn.com/2011/09/06/data‐scientist‐the-­hot­‐new­‐gig­‐in‐tech/?source=yahoo_quote</submitted‐url>
               <shortened-­url>http://lnkd.in/UUZUGT</shortened‐url>
               <title>Data scientist: The hot new gig in tech</title>
               <description>Companies that want to make sense of all their bits and bytes are hiring so‐called data scientists -­‐ if they can find any.
FORTUNE -­‐ The unemployment rate in the U.S. continues to be abysmal (9.1% in July), but the tech world...</description>
               <submitted‐image-­url>http://fortunebrainstormtech.files.wordpress.com/2011/09/data_scientists.jpg?w=340&amp;h=255</submitted-­‐image-­‐url>
               <thumbnail-­url>http://media.linkedin.com/media-­proxy/ext?w=80&amp;h=100&amp;hash=uYI7q6AkPhuioNYMcnxYI57rro0%3D&amp;url=http%3A%2F%2Ffortunebrainstormtech.files.wordpress.com%2F2011%2F09%2Fdata_scientists.jpg%3Fw%3D340%26h%3D255</thumbnail-­url>
               <eyebrow-­url>http://www.linkedin.com/share?viewLink=&amp;sid=s570040063&amp;url=http%3A%2F%2Flnkd%2Ein%2FUUZUGT&amp;urlhash=WhKu&amp;uid=5516950840016904192</eyebrow­‐url>
            </content>
            <source>
               <service­‐provider>
                  <name>LINKEDIN</name>
               </service­‐provider>
            </source>
         </share>
      </company-­status‐update>
   </update-­content>
</update>

Getting Comments and Likes on a Specific Company Update

To fetch comments on a particular company update:

Where {COMPANY UPDATE KEY} is a update/update-key representing a particular company update. By default, a company update will only return the most recent 10 comments. To retrieve all comments for a given company update paginate through them using the "start" and "count" parameters as shown above.

Use a similar syntax to retrieve the complete list of people who liked an update. By default, a company update will only return you the most recent 3 likes. To retrieve all likes for a given company update and to paginate through them: