Job Search

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 39 job boards across 98 countries through one job search API and receive a normalized 41-field dataset for applications, analytics, and automated workflows.

• 39 job platforms available through one Actor.
• 98 countries selectable in the current input schema.
• 41 normalized fields for jobs, salaries, companies, application URLs, and public contact signals.
• Public Store snapshot: 893 users and a 5.0 rating on July 21, 2026; Store content may reflect an earlier deployment.

Run a one-result test · View API

With one platform and max_results: 1, one FREE-tier result costs $0.01450: $0.01 Actor Start plus $0.00450 per result.

What does Job Search do?

Job Search is the TrueFetch Actor and job search API for collecting public job listings from multiple job boards with one input and one output contract. Provide a keyword, country, and per-platform result limit; then choose a source or let the Actor use platforms compatible with the selected market. Each published item keeps its source identity while using the same field names across platforms.

The Actor is designed for developers and data teams that need job data without maintaining a separate workflow for every board. Results can include the role, description, location, work mode, posting dates, salary, company details, application destinations, and public contact signals when a source provides them.

Job Search is not an official API of Indeed, LinkedIn, Glassdoor, or any other listed platform. It is also not an auto-apply service, candidate database, resume-ranking system, or applicant-tracking system. Source coverage, search relevance, optional filters, and field availability vary by platform.

How do I run Job Search?

1. Open Job Search on Apify.
2. Enter the three required inputs: keyword, country, and max_results.
3. For the lowest-risk first run, select one platform and set max_results to 1.
4. Click Start, inspect the Dataset item, and scale only after the fields fit your workflow.

This runnable example uses one consistent scenario throughout the README: find up to one remote Data Analyst listing from Indeed in the United States, posted within the last seven days.

{
  "keyword": "Data Analyst",
  "country": "United States",
  "platforms": ["Indeed"],
  "max_results": 1,
  "remote_only": true,
  "posted_since": "7 days",
  "job_type": "fulltime",
  "currency": "USD"
}

max_results is a limit per platform, not a total for the entire run. If you later select three platforms with max_results: 10, the run can publish up to 10 results from each platform, subject to availability.

What data does Job Search return?

The default Dataset contains 41 fields. Every item uses the same top-level field names, while values that a source or employer does not publish remain empty instead of being guessed.

Field group	Fields
Processing	processor, processed_at
Source and application	platform, platform_url, official_url, easy_apply
Role details	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 volume	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 one-result Data Analyst scenario above:

{
  "platform": "Indeed",
  "platform_url": "https://www.indeed.com/viewjob?jk=example123",
  "official_url": "https://careers.example.com/jobs/data-analyst",
  "title": "Data Analyst",
  "company_name": "Example Analytics",
  "location": {
    "raw": "Remote, United States",
    "locality": null,
    "region": null,
    "country": "United States",
    "country_code": "US"
  },
  "is_remote": true,
  "salary_minimum": 85000,
  "salary_maximum": 105000,
  "salary_currency": "USD",
  "posted_date": "2026-07-18",
  "emails": [],
  "phones": [],
  "processor": "https://apify.com/truefetch/job-search",
  "processed_at": "2026-07-20T12:00:00.000Z"
}

See the live Output schema for field types and examples.

What inputs can I configure?

Job Search exposes 10 inputs, of which 3 are required. Optional filters remain optional; omit them when a broad search better represents your intent.

Input	Required	What it controls
keyword	Yes	Job title, skill, employer, or search phrase.
country	Yes	One of 98 markets and the compatible platform set.
platforms	No	One or more of the 39 available job platforms.
max_results	Yes	Maximum published jobs per platform, from 1 to 10,000.
remote_only	No	Remote-friendly results where the source supports the filter.
distance	No	A source-side radius from 50 to 10,000 miles where supported.
location	No	City, region, postcode, or other location text; omit for a country-wide search.
posted_since	No	An absolute or relative date, such as 7 days, where supported.
job_type	No	all, fulltime, parttime, internship, or contract.
currency	No	Target currency for numeric salary conversion when usable source salary data exists.

Use the live Input schema as the final reference for accepted countries, platforms, and currencies.

What platforms and markets does Job Search cover?

The current input schema contains 39 job platforms and 98 countries. Platform availability is market-specific: not every board covers every country, and not every source supports every optional filter. If platforms is omitted, Job Search uses compatible platforms for the selected country; if it is supplied, the Actor limits the run to compatible selections.

Job platform	Job platform	Job platform
Arbetsförmedlingen	Baitoru	Bundesagentur für Arbeit
doda	France Travail	Freelancer.com
JobKorea	Jobright	Jobs2Careers
Kariyer.net	Kyujin Box	Mynavi Tenshoku
OCC	OnlineJobs.ph	SAP
Saramin	USAJOBS	Indeed
LinkedIn	Glassdoor	ZipRecruiter
Jobstreet	Glints	Stepstone
Naukri.com	Catho	foundit
Bayt.com	Reed.co.uk	Totaljobs
CV-Library	VDAB	HelloWork
InfoJobs	Job Bank	jobs.ch
Pracuj.pl	Talent.com	Jooble

Country-wide searches are possible because location is optional. Add a city, region, postcode, or local area only when the selected source supports and benefits from that constraint.

Why use Job Search?

Capability	Practical benefit
One multi-board input	Reuse the same search contract instead of preparing a separate request for every source.
One normalized 41-field dataset	Load records into analytics, data products, ATS-adjacent workflows, or AI systems with less remapping.
Source attribution	Audit every item through platform, platform_url, and, when available, official_url.
Country-aware coverage	Search appropriate boards for each selected market rather than assuming every board is global.
Controlled first run	Test one platform and one result before increasing platform count or volume.
Apify delivery	Use Datasets, exports, schedules, webhooks, API calls, or MCP after the same initial configuration.

The main trade-off is source variation. A normalized schema makes records easier to consume, but it cannot make every platform expose the same filters or fields.

Who is Job Search for?

Team	Typical use
Developers	Add multi-board job search to an application, alerting service, or internal tool.
Data engineers	Collect source-attributed job records for a warehouse or repeatable pipeline.
Analytics and research teams	Compare demand, salary, work mode, skills, and hiring activity across markets.
Job-board product teams	Build search, newsletters, monitoring, or niche vacancy products from normalized listings.
Recruiting operations	Monitor open roles across selected companies, platforms, or countries.
Sales and market intelligence	Use public hiring activity as an optional account or market signal.

Job Search is a poor fit when you need guaranteed population of every optional field, source-exclusive functionality, applications submitted on a user's behalf, or a complete historical database.

How can I use Job Search through the API or MCP?

The stable Actor ID is truefetch/job-search. The synchronous HTTP endpoint below runs the same one-result Data Analyst scenario and returns Dataset items in the response.

Run the Actor with HTTP

curl -X POST \
  "https://api.apify.com/v2/acts/truefetch~job-search/run-sync-get-dataset-items?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "keyword": "Data Analyst",
    "country": "United States",
    "platforms": ["Indeed"],
    "max_results": 1,
    "remote_only": true,
    "posted_since": "7 days",
    "job_type": "fulltime",
    "currency": "USD"
  }'

Connect the Actor through MCP

This Streamable HTTP configuration follows the current Apify MCP documentation. Replace the token placeholder with your Apify API token.

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

After connecting, use the same scenario in natural language: “Find up to one remote Data Analyst job from Indeed in the United States, posted within the last seven days, and return salary, company, and application fields.”

For asynchronous runs, SDK examples, OpenAPI, and generated snippets, use the Job Search API page.

How much does Job Search cost?

Job Search uses pay-per-event pricing: one Actor Start event for each run and one result event for every normalized job written to the default Dataset. Platform usage is included in the listed event prices.

Apify tier	Actor Start	Per result	Per 1,000 results
FREE	$0.01000	$0.00450	$4.50
BRONZE	$0.01000	$0.00435	$4.35
SILVER	$0.01000	$0.00420	$4.20
GOLD / PLATINUM / DIAMOND	$0.01000	$0.00405	$4.05

For the recommended first test, one run that publishes one result costs $0.01450 on FREE: $0.01000 for Actor Start plus $0.00450 for one result. A run that publishes no result still incurs the Actor Start event. Check the live Pricing tab before a large run because Store prices can change.

How does Job Search compare with alternatives?

Decision factor	Job Search	Single-board Actor	Separate source integrations
Coverage	39 platforms and 98 selectable countries	One platform's supported markets	Whatever the team builds and maintains
Output	One normalized 41-field schema	Source-focused schema	A team-defined schema and mapping layer
First test	One platform and one result can be tested	Usually a narrow source test	Requires each integration to be ready
Source depth	Common normalized fields across boards	Better fit for board-specific requirements	Highest potential customization
Operations	One Actor, Dataset, API, and MCP surface	One Actor per selected source	Separate maintenance for each source
Best fit	Multi-market, multi-board job data	One known source is sufficient	Bespoke control justifies ongoing ownership

Choose Job Search when breadth, repeatability, and a shared dataset matter most. Choose a related single-board TrueFetch Actor when you only need one source. Build separate integrations when source-specific behavior is more important than the time and cost of owning them.

What are the limits and troubleshooting steps?

Symptom or limit	Explanation	Next step
More results than expected	max_results applies per platform.	Reduce the limit, platform count, or both.
Results feel loosely related	Relevance follows each source board's search behavior.	Use a more specific title, skill, or employer and split mixed intents into separate runs.
A filter appears ineffective	Platforms differ in location, recency, remote, distance, and job-type support.	Test one source at a time and remove unsupported assumptions.
Some fields are empty	Sources and employers publish different information.	Make salary, company, applicant, and contact fields nullable downstream.
The same vacancy appears twice	A job can be published on multiple boards.	Deduplicate with URLs plus company, title, and location when needed.
One platform returns nothing or fails	Multi-platform runs can provide partial source coverage.	Review the run, retry the affected platform separately, and keep successful source-attributed results.
Salary is not converted	Numeric salary and a usable source currency are required.	Do not infer missing compensation; compare only populated salary records.

Before reporting a problem, rerun the smallest reproducible input: one specific keyword, one country, one platform, and max_results: 1. Include the run URL and the expected platform when opening an Apify Issue; do not include API tokens or private data.

Frequently asked questions

Is Job Search an official Indeed, LinkedIn, or Glassdoor API?

No. Job Search is an independent TrueFetch Actor on Apify and is not affiliated with or endorsed by the listed job boards. Review the applicable source terms and laws for your use case.

Do I need job-board accounts or API keys?

No job-board credentials appear in the 10 public inputs. You need an Apify account to run the Actor and an Apify API token for API or authenticated MCP access.

Is location required?

No. location is optional. Omit it for a country-wide search where supported, or add a city, region, postcode, ZIP code, or local area for a narrower query.

Is max_results the total for the whole run?

No. max_results is the maximum number of publishable jobs per platform. A value of 10 across three selected platforms can publish up to 30 results, subject to availability.

Why are some results less relevant than my keyword?

Job Search passes the search intent to each selected source, but relevance is determined by that source's search behavior. Narrow the keyword and separate unrelated roles into different runs.

What is the difference between platform_url and official_url?

platform_url identifies the listing on the source job board. official_url, when available, points to the employer's or original application destination. Either value can be empty or become unavailable after collection.

Why are salary, company, applicant, or contact fields empty?

Those values are optional because sources and employers do not publish the same details. Job Search keeps unavailable values empty instead of fabricating them.

Does Job Search remove every duplicate?

No. Repeated items within a platform search are suppressed, but the same vacancy can remain across different boards. Apply cross-platform deduplication downstream if your use case requires one canonical record.

What happens if one selected platform fails?

Other selected platforms can still return source-attributed results. Treat the Dataset as partial coverage, inspect the run, and retry a required source separately.

Can I schedule recurring searches?

Yes. Apify schedules and webhooks can run the Actor on a recurring basis and send Dataset results to downstream systems. Confirm your result volume and expected event cost before scheduling a multi-platform search.

Related TrueFetch Actors

• Indeed Job Listing — a narrower input for Indeed listings.
• LinkedIn Job Listing — LinkedIn jobs and application fields.
• Glassdoor Job Listing — Glassdoor jobs, salaries, and company-rating fields.

Support and last updated

• Run Job Search
• 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 the older deployed Store content; public Store statistics are dated snapshots.

Run one result first, verify the source relevance and fields for your market, then scale the platform count and volume.

Run a one-result test · View API