LinkedIn Job Listing

Affiliate disclosure: TrueFetch may earn a commission if you sign up through an Apify link on this page, at no extra cost to you.

Search public LinkedIn job listings across 98 countries and turn source-specific roles into a normalized 41-field Dataset for hiring intelligence and labor-market workflows.

• 98 country markets selectable in the current local input schema.
• Recency, remote, job-type, location, and distance filters can be combined in one LinkedIn search.
• 41 normalized fields cover roles, applicants, compensation, companies, applications, and public contact signals.
• Public Store snapshot: 297 users and a 5.0 rating on July 21, 2026; deployed Store content may reflect an earlier release.

Run a one-result test · View API

With max_results: 1, one FREE-tier result costs $0.01375: $0.01000 for Actor Start plus $0.00375 for one published result.

What does LinkedIn Job Listing do?

LinkedIn Job Listing is a TrueFetch Actor and LinkedIn jobs API for collecting public vacancies by keyword and country. Optional inputs narrow the request by location, search radius, posting age, remote preference, or employment type. Each accepted job is normalized into the same Dataset fields so repeat runs can feed a stable downstream contract.

The Actor is designed for teams that need current vacancy signals, source URLs, role attributes, applicant counts when visible, compensation when disclosed, and company context without maintaining a separate data collector. It can support recruiting research, workforce analytics, product features, job alerts, and hiring-intent analysis.

LinkedIn Job Listing is independent of LinkedIn and is not an official LinkedIn API. It does not access private profiles, scrape resumes, identify candidates, send messages, or submit applications. Public page availability, search relevance, applicant counts, salary values, and company details vary by listing and market.

How do I run LinkedIn Job Listing?

1. Open LinkedIn Job Listing on Apify.
2. Supply the required keyword, country, and max_results values.
3. Add only the location and filters that express your intended LinkedIn search.
4. Run one result first, inspect the Dataset, and scale after confirming relevance.

The examples below share one scenario: find one contract Product Designer role in Singapore, posted within the last three days, within a 50-mile search radius, and convert usable salary values to SGD.

{
  "keyword": "Product Designer",
  "country": "Singapore",
  "max_results": 1,
  "location": "Singapore",
  "distance": 50,
  "posted_since": "3 days",
  "job_type": "contract",
  "currency": "SGD"
}

max_results limits published LinkedIn jobs for the run. It does not guarantee that the public search will expose that many accessible and relevant listings.

What data does LinkedIn Job Listing return?

The default Dataset defines 41 fields. Unavailable values remain empty; the Actor does not manufacture salary, applicant, company, or application details.

Field group	Fields
Processing	processor, processed_at
Source and application	platform, platform_url, official_url, easy_apply
Role taxonomy	title, description, job_type, job_level, job_function, listing_type, skills, experience_range
Location and work mode	location, is_remote, work_from_home
Dates and demand	posted_date, valid_through, applicant_count, vacancy_count
Compensation	salary_minimum, salary_maximum, salary_currency, salary_period
Company	company_name, company_type, company_founded, company_industry, company_url, company_website, company_logo, company_addresses, company_revenue, company_description, company_rating, employee_count, review_count
Public contacts	emails, phones, social_links

This abbreviated, illustrative item matches the Singapore Product Designer scenario:

{
  "platform": "LinkedIn",
  "platform_url": "https://www.linkedin.com/jobs/view/1234567890",
  "official_url": null,
  "title": "Product Designer",
  "company_name": "Example Product Studio",
  "location": {
    "raw": "Singapore",
    "locality": "Singapore",
    "country": "Singapore",
    "country_code": "SG"
  },
  "posted_date": "2026-07-20",
  "applicant_count": 24,
  "job_type": "Contract",
  "job_level": "Mid-Senior level",
  "job_function": "Design",
  "salary_currency": "SGD",
  "processor": "https://apify.com/truefetch/linkedin-job-listing",
  "processed_at": "2026-07-21T12:00:00.000Z"
}

Use the live Output schema for field types and representative examples.

What inputs can I configure?

The current local schema exposes 9 inputs, with 3 required.

Input	Required	What it controls
keyword	Yes	Job title, skill, employer, or search phrase.
country	Yes	One of the 98 supported country markets.
max_results	Yes	Maximum published jobs, from 1 to 10,000.
remote_only	No	Restricts the LinkedIn search to remote-friendly roles.
distance	No	Search radius from 50 to 10,000 miles.
location	No	City, region, postcode, or local search text; omit it for a country-level search.
posted_since	No	Absolute or relative posting age such as 3 days.
job_type	No	all, fulltime, parttime, internship, or contract.
currency	No	Target currency for conversion of usable numeric salary data.

Recency, remote preference, job type, and distance are separate LinkedIn request filters and can be combined. currency is applied to salary values after collection and does not change ranking or listing availability. Review the Input schema before automation.

What platforms and markets does LinkedIn Job Listing cover?

This is a single-platform Actor: it searches LinkedIn jobs. The local schema contains 98 countries:

Algeria, Angola, Argentina, Australia, Austria, Azerbaijan, Bahrain, Bangladesh, Belgium, Bosnia and Herzegovina, Brazil, Bulgaria, Cameroon, Canada, Chile, China, Colombia, Costa Rica, Croatia, Cyprus, Czechia, Denmark, Dominican Republic, Ecuador, Egypt, El Salvador, Estonia, Finland, France, Germany, Ghana, Greece, Guatemala, Hong Kong, Hungary, India, Indonesia, Iraq, Ireland, Israel, Italy, Ivory Coast, Japan, Jordan, Kazakhstan, Kenya, Kuwait, Latvia, Lebanon, Libya, Lithuania, Luxembourg, Malaysia, Malta, Mexico, Morocco, Mozambique, Netherlands, New Zealand, Nigeria, Norway, Oman, Pakistan, Panama, Peru, Philippines, Poland, Portugal, Puerto Rico, Qatar, Romania, Russia, Saudi Arabia, Senegal, Serbia, Singapore, Slovakia, Slovenia, South Africa, South Korea, Spain, Sweden, Switzerland, Taiwan, Thailand, Tunisia, Turkey, Uganda, Ukraine, United Arab Emirates, United Kingdom, United States, Uruguay, Uzbekistan, Venezuela, Vietnam, Yemen, and Zambia.

If location is omitted, the selected country becomes the search location. If a city or region is supplied without the country name, the request keeps that local text associated with the chosen country. Coverage and result density still depend on LinkedIn's public listings in that market.

Why use LinkedIn Job Listing?

Capability	Practical benefit
LinkedIn-focused search	Use a narrow source contract when LinkedIn is the required board.
Combined public filters	Express role, market, recency, work mode, employment type, and radius in one run.
Normalized role taxonomy	Compare populated seniority, function, employment type, and skills fields across repeat searches.
Applicant and company context	Capture visible demand and employer signals without treating missing values as facts.
Source attribution	Preserve the listing URL and a separate official destination when one is available.
Apify delivery	Reuse the same input through the Console, API, schedules, webhooks, or MCP.

The trade-off is that public LinkedIn data is variable. A stable schema simplifies consumption, but it cannot force every listing to publish salary, applicant, or company information.

Who is LinkedIn Job Listing for?

Team	Typical use
Product developers	Add LinkedIn vacancy search to a job product or internal research tool.
Data teams	Build repeatable snapshots of role demand by market, function, or seniority.
Recruiting operations	Monitor new openings without mixing several job boards in the same run.
Workforce analysts	Study posted roles, employment types, remote signals, and disclosed pay.
B2B intelligence teams	Use hiring activity as one source-attributed company signal.

The Actor is not suitable for private-profile data, candidate contact extraction, recruiter messaging, applications, or guaranteed complete company profiles.

How can I use LinkedIn Job Listing through the API or MCP?

The stable Actor ID is truefetch/linkedin-job-listing. This synchronous HTTP request runs the shared Singapore scenario:

curl -X POST \
  "https://api.apify.com/v2/acts/truefetch~linkedin-job-listing/run-sync-get-dataset-items?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "keyword": "Product Designer",
    "country": "Singapore",
    "max_results": 1,
    "location": "Singapore",
    "distance": 50,
    "posted_since": "3 days",
    "job_type": "contract",
    "currency": "SGD"
  }'

This configuration follows the current Apify MCP documentation and limits the available tool to this Actor:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=truefetch/linkedin-job-listing",
      "headers": {
        "Authorization": "Bearer <APIFY_TOKEN>"
      }
    }
  }
}

Ask the connected client for the same one-result Product Designer scenario. The API page provides asynchronous, SDK, and OpenAPI options.

How much does LinkedIn Job Listing cost?

Billing uses one Actor Start event per run and one result event per normalized job written to the default Dataset.

Apify tier	Actor Start	Per result	Per 1,000 results
FREE	$0.01000	$0.00375	$3.75
BRONZE	$0.01000	$0.00363	$3.63
SILVER	$0.01000	$0.00350	$3.50
GOLD / PLATINUM / DIAMOND	$0.01000	$0.00338	$3.38

The recommended one-result FREE-tier test costs $0.01375 when a result is published. Actor Start still applies when no result is produced. Confirm current amounts on the Pricing tab before scaling.

How does LinkedIn Job Listing compare with alternatives?

Decision factor	LinkedIn Job Listing	Multi-board Job Search	Manual LinkedIn browsing
Source	LinkedIn only	Several compatible boards	LinkedIn only
Output	Structured 41-field Dataset	Shared multi-source schema	Human-readable pages
Repeatability	Saved input, API, MCP, schedules	Same, with broader source scope	Manual steps and copying
Best fit	LinkedIn-specific hiring signals	Cross-board coverage	Occasional one-off review
Main trade-off	Public fields can be sparse	Source depth is normalized	No reliable structured pipeline

Choose LinkedIn Job Listing when LinkedIn is a required source and repeatable structured output matters. Choose Job Search when board diversity is more important than source-specific focus.

What are the limits and troubleshooting steps?

Symptom or limit	Explanation	Next step
Results are fewer than max_results	The value is a cap; public availability and relevance determine actual volume.	Broaden the keyword, location, or posting window.
A country-wide query feels broad	Without location, LinkedIn searches the selected country.	Add a city or region and an appropriate distance.
Some role attributes are empty	Seniority, function, skills, and employment type are not visible on every listing.	Keep these fields nullable downstream.
Applicant count is empty	LinkedIn does not always display an applicant count publicly.	Do not interpret null as zero applicants.
Salary is missing or unchanged	Conversion needs disclosed numeric pay, a source currency, and available exchange rates.	Compare only populated salary records.
official_url is empty	A separate employer destination is not always exposed.	Use platform_url to retain source attribution.
A listing disappears between runs	Public vacancies can close, change, or become unavailable.	Store collection timestamps and treat each run as a snapshot.

For support, reproduce the problem with one keyword, one country, and max_results: 1, then share the run URL through Apify Issues. Do not share API tokens.

Frequently asked questions

Does LinkedIn Job Listing require a LinkedIn account?

No LinkedIn credentials or cookies are public inputs. An Apify account is needed to run the Actor, and an Apify token is required for authenticated API or MCP use.

Is location required?

No. The country is used as the search location when location is omitted. Add local text for a narrower market.

Can recency, remote, and job type be combined?

Yes. These inputs map to separate search constraints for LinkedIn and can be supplied together, subject to source availability.

Does distance apply without a city?

The distance value can be sent with the country-level search, but it is usually more meaningful with a specific city or region.

Why is easy_apply or official_url empty?

The normalized Dataset contains those fields, but public LinkedIn pages do not expose them consistently. Empty means unavailable, not false.

Does currency filter LinkedIn jobs?

No. It requests post-collection conversion of usable salary numbers and does not affect search ranking.

Can I use this Actor for recurring hiring-intent monitoring?

Yes. Schedule a tested input and compare timestamped results over time. Account for reposted vacancies and changing public fields in your deduplication logic.

Related TrueFetch Actors

• Indeed Job Listing — choose it for an Indeed-only search contract and Indeed market coverage.
• Glassdoor Job Listing — choose it when Glassdoor listings and company-rating context are central.
• Job Search — choose it for one normalized request across multiple compatible boards.

Support and last updated

• Run LinkedIn Job Listing
• View the API
• Report an issue
• Join the TrueFetch Telegram group
• Contact support on Telegram

Last updated: July 21, 2026. Local schema, metadata, pricing, and read-only runtime evidence were verified separately from inconsistent older Store snapshots; public Store statistics are dated observations.

Run one result first, confirm the LinkedIn fields and relevance needed by your workflow, and then increase volume.

Run a one-result test · View API