Page Comparison

...

Overview

The following operations allow you to work with Companies. Click an operation name to see details on how to use it.

For a sample proxy service the illustrates how to work with companies, see Sample configuration. 

Operation details

This section provides details on each of the operations.

...

The Company Profile API retrieves and displays one or more company profiles based on the company ID or universal name. Also, it returns basic company profile data such as name, Web site, and industry, and handles additional company content such as RSS stream and Twitter feed.

<linkedin.companyLookup>
	<companyId>{$ctx:companyId}</companyId>
    <universalName>{$ctx:universalName}</universalName>
    <emailDomains>{$ctx:emailDomains}</emailDomains>
    <companyAdmin>{$ctx:companyAdmin}</companyAdmin>
    <fieldSelectors>{$ctx:fieldSelectors}</fieldSelectors>
</linkedin.companyLookup>

Properties

• companyId: The unique internal numeric company identifier.

• universalName: Required - The unique string identifier for a company.  

• emailDomains: Company email domains.

• companyAdmin: Lists all the companies that the authenticated user is an administrator of.

• fieldSelectors: Field selectors are specified after the resource identifiers and path components of a resource, prefixed by a colon, contained within parentheses, and separated by commas. Fields will be returned in the order specified. When URL-encoding your resource URLs, ensure that the parentheses used in selectors remain un-escaped. Remember, each field you select adds computation time to your API request. It's best to be very specific as to what fields you want returned in each API call you make.

1 = considered parameter    0 = not considered parameter

...

...

Overview

The following operations allow you to work with Companies. Click an operation name to see details on how to use it.

For a sample proxy service the illustrates how to work with companies, see Sample configuration. 

Operation details

This section provides details on each of the operations.

Anchor
companyLookup companyLookup

Company lookup API and fields

The Company Profile API retrieves and displays one or more company profiles based on the company ID or universal name. Also, it returns basic company profile data such as name, Web site, and industry, and handles additional company content such as RSS stream and Twitter feed.

<linkedin.companyLookup>
	<companyId>{$ctx:companyId}</companyId>
    <universalName>{$ctx:universalName}</universalName>
    <emailDomains>{$ctx:emailDomains}</emailDomains>
    <companyAdmin>{$ctx:companyAdmin}</companyAdmin>
    <fieldSelectors>{$ctx:fieldSelectors}</fieldSelectors>
</linkedin.companyLookup>

Properties

• companyId: The unique internal numeric company identifier.

• universalName: Required - The unique string identifier for a company.  

• emailDomains: Company email domains.

• companyAdmin: Lists all the companies that the authenticated user is an administrator of.

• fieldSelectors: Field selectors are specified after the resource identifiers and path components of a resource, prefixed by a colon, contained within parentheses, and separated by commas. Fields will be returned in the order specified. When URL-encoding your resource URLs, ensure that the parentheses used in selectors remain un-escaped. Remember, each field you select adds computation time to your API request. It's best to be very specific as to what fields you want returned in each API call you make.

{
"accessToken":"AQUTf-7ouUMipARXfNVowT6ikytQsmVdf3VIo648_iksSI4uBeAv5aqlmpoL0_m4nZ3bG8nyK7wqZRyJKqLTsOAHLDnGpqGf0tFb8F4pSy_dtbJoaFGuIdoD8PjipKpyIorZXgR1wjpyynowzEJ9YX9Poj6AXbRWTRsnKpRNZzwEQB4YAv8",
"apiUrl":"https://api.linkedin.com

",
"companyId":"162479",
"universalName":"linkedin",
"emailDomains":"apple.com",
"companyAdmin":"true",
"fieldSelectors":"id"
}

<linkedin.checkAdminMember>
    <companyId>{$ctx:companyId}</companyId>
</linkedin.checkAdminMember>

{
"apiUrl":"https://api.linkedin.com

",
"accessToken":"AQUDwVyNpxmDdVgdBB0V3yOrdyeEpbaPoZveoYH5jH5p-dIVBRyGZoeU2l0JaHv4LhLa0sOjZgBkS2TCN8V5ilZ3h3pKb_2Nkym2gvSXEWyvg-wqbExzXuLS1s9oMRB_jzmVHSFGDbQCLczvqpi_IwbPSfnKjw4ySISwI5T_W44Q1cWQ2eY",
"companyId":"32873"
}

Add a comment on Company page.

AddComment method allows to submit a comment on a company update. 

<linkedin.addComment>
    <companyId>{$ctx:companyId}</companyId>
    <updateKey>{$ctx:updateKey}</updateKey>
    <comment>{$ctx:comment}</comment>
</linkedin.addComment>

Properties

• companyId: The unique internal numeric company identifier.

Sample request 

Following is a sample REST request that can be handled by

...

the addComment operation.

...

...

{

...

"apiUrl":"https://api.linkedin.com",
"

...

accessToken":"

...

AQUDwVyNpxmDdVgdBB0V3yOrdyeEpbaPoZveoYH5jH5p-dIVBRyGZoeU2l0JaHv4LhLa0sOjZgBkS2TCN8V5ilZ3h3pKb_2Nkym2gvSXEWyvg-wqbExzXuLS1s9oMRB_jzmVHSFGDbQCLczvqpi_IwbPSfnKjw4ySISwI5T_W44Q1cWQ2eY",
"

...

companyId":"

...

2414183",
"

...

updateKey":"

...

PDATE-c2414183-6029016796592427008",
"

...

comment":"

...

test"

...

...

}

...

Related

...

LinkedIn documentation

https://developer.linkedin.com/docs/company-

...

pages#company_comment

Anchor
searchCompanyPage searchCompanyPage

Company search

Use the Company Search API to find companies using keywords, industry, or location. It returns a collection of matching companies. Each entry can contain much of the information available on the company page.

...

• refineResults: Comma separated values refine the results that need to be retrieved from the API. For example, the above method would return the facets, ID and Web site URL of the company.

• keywords: Companies that have all the keywords anywhere in their listing. Multiple words should be separated by a space. (Don't forget to URL encode this data.)
• isHqOnly: Matching companies by the location of the headquarters. When this is set to "true" and a location facet is used, this restricts returned companies to only those whose headquarters resides in the specified location.
• facet: Facet values to search over.
• facets: Facet buckets to return.
• start: Start location within the result set for paginated returns. This is the zero-based ordinal number of the search return, not the number of the page. To see the second page of 10 results per page, specify 10, not 1. Ranges are specified with a starting index and a number of results (count) to return. The default value is 0.
• count: The number of jobs to return. Values can range between 0 and 110. The default value is 10. The total number of results available to any user depends on the user's account level.
• sort: Controls the search result order. Options would be relevance or relationship.

Sample request

Following is a sample REST request that can be handled by the searchCompanyPage operation.

...

• companyId: Required - The unique ID for the suggested company.

Sample request

Following is a sample REST request that can be handled by the checkShare operation.

...

• companyId: Required - The unique ID for the suggested company.

• properties: specify the needed fields(id,name,description).

Sample request

Following is a sample REST request that can be handled by the getAdditionalProfileInfo operation.

...

• companyId: Required - The unique ID for the suggested company.

• updateKey: The unique identifier for company update.

Sample request

Following is a sample REST request that can be handled by the getAdditionalProfileInfo operation.

...

https://developer.linkedin.com/docs/company-pages#get_update_comments

Anchor
getCompanyUpdate getCompanyUpdate

Update the company profile.

...

• companyId: Required - The unique ID for the suggested company.

• count: Maximum number of updates to return.

• start: The offset value for paginating update results.

Sample request

Following is a sample REST request that can be handled by the getCompanySpecificUpdate operation.

...

• companyId: Required - The unique ID for the suggested company.

• updateKey: The unique identifier for company update.

Sample request

Following is a sample REST request that can be handled by the getCompanySpecificUpdate operation.

...

• companyId: Required - The unique ID for the suggested company.

• geos : Segment by a particular geographic area.

• jobFunc : Segment by a particular company size targeting code.

• industries : Segment by member industry.

• seniorities: Segment by member seniority level targeting code.

• companySizes : Segment by a particular geographic area.

Sample request

Following is a sample REST request that can be handled by the getfollowers operation.

...

• companyId: Required - The unique ID for the suggested company.

• timeGranularity: Granularity of statistics eg values:day,month.

• startTimestamp: Starting timestamp of when the stats search should begin (milliseconds since epoch).

• endTimestamp: Ending timestamp of when the stats search should end (milliseconds since epoch).

Sample request

Following is a sample REST request that can be handled by the getHistoricalFollowers operation.

...

• companyId: Required - The unique ID for the suggested company.

• udateKeyupdateKey: The unique identifier for company update.

...