Hiring Intent Leads — Public Company Job Boards

Find companies with matching open roles on Greenhouse and Lever, with a direct job link and source evidence for every returned company. Use hiring activity to prioritize account research, recruitment services, or relevant B2B outreach. A job posting does not prove buying intent, an approved budget, or a decision-maker's identity.

No paid data-provider API key is needed in public-board mode. Apify Actor fees and platform usage still apply. You supply target companies' board URLs; this is not a whole-web company discovery service.

Try a small run

Open the two-company public-board example.

Keep the prefilled public-board mode and two example companies, set the title to Engineer, leave location blank, and request two company records. The sample disables email enrichment because it does not supply employer websites. Set a small run-cost limit and timeout before starting. Public postings change; a valid board can have no matching jobs.

Replace the examples with your own Greenhouse or Lever board URLs. String URLs work, or use objects with url, companyName, and companyWebsite. Only add companyWebsite when you have verified the employer's public website; it is used for optional email extraction and is marked as input-supplied in the output.

Example input:

{
  "source": "job_boards",
  "jobBoards": [
    { "url": "https://job-boards.greenhouse.io/greenhouse", "companyName": "Greenhouse" },
    { "url": "https://jobs.lever.co/spotify", "companyName": "Spotify" }
  ],
  "jobTitle": "Engineer",
  "location": "",
  "maxResults": 2,
  "enrichEmails": false,
  "verifyEmails": false,
  "outputFormat": "full"
}

Supported sources and coverage

• Greenhouse: boards.greenhouse.io or job-boards.greenhouse.io company boards.
• Lever: jobs.lever.co and jobs.eu.lever.co company boards.
• Google Jobs: retained as an explicitly unreliable legacy option. Recent tests were blocked. Use board mode when you have target-company URLs.

Automatic mode chooses board mode when jobBoards is supplied; otherwise it keeps the legacy Google Jobs behavior for existing integrations. The new prefilled example explicitly selects board mode. No silent substitution of unrelated companies occurs.

Board mode accepts up to 20 boards. It returns at most one representative matching job per company, not every vacancy, and deduplicates shared company names or supplied websites. The result cap is a ceiling; two boards can return no more than two company records. Title and location filters use case-insensitive word matching. Blank filters include any role/location. Remote matching requires source evidence; locations are not geocoded.

Lever pages are bounded to 1,000 postings per board and Greenhouse matching to 5,000. Incomplete coverage is reported in OUTPUT_SUMMARY. All source failures fail the run; partial results identify failed/capped boards. A valid completed search with no matches returns zero records. A zero-match search with source failures or a scan cap fails explicitly.

Output and email evidence

Full output contains companyName, companyNameSource, companyWebsite, companyWebsiteSource, jobTitle, jobLocation, jobSource, jobUrl, jobBoardUrl, jobId, hiringSignal, email, verification evidence, allEmails, and scrapedAt. Name provenance is input, job_board, or board_identifier. Employer websites are never inferred from the board slug. Missing contact information remains blank.

Email extraction is optional and requires a usable employer website. SMTP verification can be blocked or inconclusive. A true emailVerified value requires acceptance of the recipient and rejection of a random-recipient probe. DNS MX evidence is separate, and no delivery or bounce rate is guaranteed. HubSpot and Salesforce layouts may require custom-field mapping.

Repeat account monitoring

Save your target-board list as an Apify task and rerun it on your chosen schedule. Compare jobId/jobUrl and company identifiers between datasets to find changed hiring activity. This actor does not persist a cross-run change history or send outreach. Use the source posting to assess relevance before contacting a business.

Pricing and support

The current base event is $50 per 1,000 returned company records. For example, two returned records are $0.10 in base result fees, before any other configured events, platform usage, or applicable plan discounts. A returned company record is chargeable even if it has no email. Check the live Pricing tab for the complete current charges. Provider API credits are not needed for Greenhouse/Lever reads.

For an issue, include a current run link, source mode, board URLs, filters, and the expected versus observed result. Do not post API tokens or private customer data.

Source references: Greenhouse public job-board API and Lever public postings API.