LinkedIn API by APISH

Get public LinkedIn data as clean, consistent JSON: linkedIn article, linkedIn company, linkedIn company posts, one LinkedIn job, linkedIn job search, linkedIn post and more. 8 endpoints, one response shape, numbers parsed, absolute URLs.

How to use

1. Pick an Endpoint. Each option shows what it returns and its price in credits.
2. Enter its Parameters as JSON, for example {"url":"https://www.linkedin.com/pulse/affordable-climate-win-look-sky-bill-gates-eoj7e"}. All parameters are listed below.
3. Run. Each call becomes one row in the dataset. Use Batch to run the same endpoint for many inputs and Pages per input to follow pagination.

Pricing

Pay per event: you pay per APISH credit the call used. The price of each endpoint is in the table below. Calls that fail on our side (server errors, timeouts, blocks) are free.

Endpoints

Endpoint	Returns	Required parameters	Credits
/linkedin/v1/article	LinkedIn article	url	1
/linkedin/v1/company	LinkedIn company	url	1
/linkedin/v1/company/posts	LinkedIn company posts	url	1
/linkedin/v1/job	One LinkedIn job	url	1
/linkedin/v1/jobs	LinkedIn job search	keywords, location	1
/linkedin/v1/post	LinkedIn post	url	1
/linkedin/v1/post/transcript	LinkedIn video post transcript	url	1
/linkedin/v1/profile	Public LinkedIn profile	url	1

Output

Each dataset row has endpoint, params, status, credits_used and the endpoint's data. Add "raw": 1 to the parameters to also get the site's original record, or "fields": "a,b.c" to return only the fields you need.

Endpoint details

LinkedIn article

Endpoint /linkedin/v1/article · 1 credit per successful call.

Parameters:

• url (required)

Example parameters: {"url":"https://www.linkedin.com/pulse/affordable-climate-win-look-sky-bill-gates-eoj7e"}

LinkedIn company

Endpoint /linkedin/v1/company · 1 credit per successful call.

Parameters:

• url (required): Company URL or slug.

Example parameters: {"url":"google"}

LinkedIn company posts

Endpoint /linkedin/v1/company/posts · 1 credit per successful call.

Parameters:

• url (required)

Example parameters: {"url":"https://www.linkedin.com/company/microsoft"}

One LinkedIn job

Endpoint /linkedin/v1/job · 1 credit per successful call.

Parameters:

• url (required): Job URL or numeric id.

Example parameters: {"url":"https://www.linkedin.com/jobs/view/senior-software-engineer-python-at-venmo-4465379983"}

LinkedIn job search

Endpoint /linkedin/v1/jobs · 1 credit per successful call.

Pagination: result offset (25 per page). Pass next_start from the previous response.

Parameters:

• keywords (required)
• location (required): Place name. Pass geo_id instead to search by LinkedIn's geo id (location can then be left out).
• geo_id: LinkedIn's numeric geo id (in a LinkedIn jobs URL as geoId); replaces location.
• distance — one of 0, 5, 10, 25, 50, 100: Miles around the location: 0, 5, 10, 25, 50 or 100.
• posted — one of any, 24h, week, month: Date posted: 24h, week, month, or a number of seconds.
• easy_apply: Only Easy Apply jobs.
• company_id: LinkedIn company ids, comma separated (up to 10), from the company's jobs link (f_C).
• start: Result offset (25 per page). Pass next_start from the previous response.

Example parameters: {"keywords":"python","location":"Texas"}

LinkedIn post

Endpoint /linkedin/v1/post · 1 credit per successful call.

Parameters:

• url (required)

Example parameters: {"url":"https://www.linkedin.com/posts/microsoft_this-month-the-microsoft-atlanta-team-in-activity-7516505833061474305-T6ou"}

LinkedIn video post transcript

Endpoint /linkedin/v1/post/transcript · 1 credit per successful call.

Parameters:

• url (required)

Example parameters: {"url":"https://www.linkedin.com/posts/microsoft_this-month-the-microsoft-atlanta-team-in-activity-7516505833061474305-T6ou"}

Public LinkedIn profile

Endpoint /linkedin/v1/profile · 1 credit per successful call.

Parameters:

• url (required): Profile URL or public id.

Example parameters: {"url":"williamhgates"}

Support

Questions, bugs or a missing field? Open an issue in this Actor's Issues tab and we will reply there.

Public data only: nothing behind a login. You are responsible for how you use the data you collect.