Career Site Jobs Aggregator

What this Actor does

Aggregate public employer job listings from Greenhouse, Lever, Ashby, and Rippling career-site feeds with keyword, location, company, and ATS filters.

Input example

{
  "q": "engineer",
  "location": "remote",
  "companies": [
    "stripe",
    "openai",
    "plaid"
  ],
  "ats": [
    "greenhouse",
    "ashby"
  ],
  "limit": 25
}

Input fields

Search configured public employer career-site feeds.

• q (string, user input): Keyword searched across job title, company, department, location, employment type, and description. Leave empty only when using company or ATS filters.
• location (string, user input): Optional location substring such as remote, New York, San Francisco, London, or Israel. The match is substring-based against normalized location text.
• companies (array, user input): Optional configured company slugs to search. Use values from the supported company catalog, for example stripe, openai, plaid, anthropic, ramp, or datadog.
• ats (array, user input): Optional applicant tracking system filters. v1 supports public Greenhouse, Lever, Ashby, and Rippling career feeds.
• limit (integer, user input): Maximum jobs to return, 1-100.
• searches (array, user input): Optional array of search objects for batch mode, for example [{"q":"engineer","location":"remote","companies":["stripe"],"limit":10}]. If present, the Actor runs each object as a separate /jobs search and pushes all returned jobs.
• apiBaseUrl (string, optional override): Override of the upstream API base URL. Defaults to runtime.baseUrl from service.json.

Output dataset

Each dataset item is one normalized public employer job.

• jobId: ATS job identifier.
• title: Job title.
• company: Hiring company.
• ats: Source ATS.
• location: Primary job location.
• department: Department or team.
• employmentType: Employment type when available.
• applyUrl: Employer apply URL.

Developer notes

Set CAREER_SITE_JOBS_AGGREGATOR_API_KEY as an Apify secret environment variable. The Actor forwards it as X-API-Key to the upstream API. Use apiBaseUrl only for local or staging QA. Production runs default to the deployed API base URL from service.json. For advanced testing, a requests array can call explicit API paths; normal users should use the service-specific fields above.

Run locally

$apify run

Deploy

$apify push