Greenhouse Jobs API avatar

Greenhouse Jobs API

Pricing

from $1.20 / 1,000 job records

Go to Apify Store
Greenhouse Jobs API

Greenhouse Jobs API

Find job postings from Greenhouse-powered career sites by country, role, company, salary, posting age, employment type, and seniority.

Pricing

from $1.20 / 1,000 job records

Rating

0.0

(0)

Developer

Aspen Technology Labs, Inc.

Aspen Technology Labs, Inc.

Maintained by Community

Actor stats

0

Bookmarked

1

Total users

1

Monthly active users

2 days ago

Last modified

Features

Limited permissions

Share

Greenhouse Job Postings API - JobsIndex by Aspen Tech Labs

Greenhouse is one of the most widely adopted ATS platforms, particularly among technology and machine learning companies, high-growth businesses, and teams that take a structured approach to hiring.

The JobsIndex API, built by Aspen Tech Labs, collects job postings directly from the Greenhouse ATS across thousands of companies worldwide. It is part of a broader index aggregating 11M+ active job listings daily from 300K+ employer source sites globally.

Coverage is not limited by posting date. If a job was posted six months ago, a year ago, or longer, as long as it is an actual live job posting, we have it in our index. We actively verify that every position is current and not an abandoned posting. Our database also includes evergreen roles that companies keep open on a rolling basis, which we tag in the system.

What You Can Use It For

This Actor serves two primary use cases: teams that want to publish Greenhouse job listings on their platform, and teams that need structured Greenhouse ATS data for matching algorithms, AI model training, or tech hiring intelligence.

This Actor can power job boards and careers platforms with live Greenhouse postings, and feed matching engines, AI models, and hiring intelligence tools with data filterable by role, location, or posting date.

Need More Or Something Different?

If this Actor is working well for you, we'd love a review. For more data, custom feeds, feedback, or any questions, reach out via our website or email. You can also explore JobMarketPulse, our labor and job market intelligence platform.

Built-In Search Preset

This Actor is fixed internally to Greenhouse-powered jobs (ats_name=greenhouse). The ATS/source platform preset is not exposed as an input parameter. Users can narrow the search by country, structured location, role keywords, salary, company, category, posting age, employment type, seniority, work arrangement, and pagination fields.

Quick Start

{
"what": "@title software engineer",
"country": "United States",
"page": 0,
"size": 5
}

Input Parameters

ParameterDescriptionExample
idOptional JobsIndex job ID filter. Use this to retrieve a known job record.15131474020159014052
salarySalary amount or range filter.20h-30h
whatMain job search query. Supports keywords, boolean logic, exact phrases, and field-targeted search such as @title software engineer or @(title,description) (python).@title software engineer
whereFree-text location search. Supports place names, boolean logic, and field-targeted search such as @country United States or @(city,metro_area) (San Francisco). Prefer structured location fields for exact filters.United States
countryCountry filter.United States
regionState, province, or region.California
cityCity filter.San Francisco
postal_codePostal or ZIP code filter.94105
metro_areaMetropolitan area filter.San Francisco-Oakland-Fremont, CA
titleJob title filter.Software Engineer
company_nameCompany name filter.Stripe
company_domainCompany website domain.stripe.com
categoryJob category.Information Technology
sub_categoryMore specific job function or role.Software Developer
industryCompany industry filter.Software
remoteWork arrangement filter. Supported values: remote, on-site, hybrid.remote
collar_typeOptional job classification filter: Healthcare, White (white-collar), or Blue (blue-collar). Omit or leave empty for no filter.White
postedRelative posting age or ISO date.1w
employment_typeEmployment type.Full-Time
senioritySeniority level.Senior
pagePage number, starting from 0.0
sizeNumber of results per page. Default 5, min 1, max 100.5

Salary Filter Format

Use:

NUMBER[UNIT]

or:

NUMBER[UNIT]-NUMBER[UNIT]

Supported units:

  • h - per hour
  • d - per day
  • w - per week
  • m - per month
  • y - per year

Examples:

  • 20h-30h - hourly rate between 20 and 30
  • 35h - fixed hourly rate
  • 20h-200000y - range from hourly to yearly comparison

Advanced Filters

what and where support plain-text search, boolean logic, and field-targeted search.

If no field is provided, the API expands the search across a default set of relevant fields.

Plain keyword examples:

what = front end engineer
where = United States

Field-specific examples:

what = @title software engineer
where = @country United States

Multi-field examples:

what = @(title,description) (python)
what = @(title,title_raw,description) (engineer OR manager)
what = @(title,description) (machine AND learning)
where = @(country,region,city,metro_area,county,sub_city) (United States)
where = @(city,region,metro_area) (San Francisco OR California)
where = @(city,region,metro_area) (California)

Structured Filter Precedence

When using what or where, avoid sending separate structured filters for the same search unless you want those structured filters to take priority.

  • For where, location fields such as country, region, city, postal_code, and metro_area take priority and can override or narrow the free-text location query.
  • For what, structured job filters such as title, company_name, company_domain, category, sub_category, industry, posted, salary, employment_type, remote, and seniority take priority and can override or narrow the keyword query. For example, sub_category = Registered Nurse takes priority over what = engineer.

collar_type is a standalone filter that narrows the results of what without replacing it. If the two filters specify conflicting collar types, the search returns no matches.

Use what and where as free-text searches when their corresponding structured filters are not set.

Common job/content fields for what:

  • title, title_raw, description, reference
  • category, sub_category, seniority, industry, company_type
  • company_name, company_domain, company_name_raw
  • employment_type, remote, language
  • posted, posted_raw, expired
  • url_source, url_apply
  • salary_value, salary_currency, salary_unit
  • id

Common location fields for where:

  • country, region, city, metro_area, county, sub_city, postal_code

Location Filtering

For precise location matching, use structured filters exposed for this Actor:

  • country
  • region
  • city
  • postal_code
  • metro_area

Use where only as a free-text location search when the structured location filters above are not set. If where is provided together with structured location filters, the structured filters take priority and where may be ignored or deprioritized.

Limits and Pagination

This Actor uses the JobsIndex jobs API. Results are paginated with page and size.

ParameterDefaultMinMax
page00Depends on size and the item cap
size51100

Individual numeric bounds are checked before a run starts. Query-dependent pagination is checked after the run starts, as explained below.

One Run, One Page

Each run requests one page, not all available pages. size is the requested number of jobs for that page, with an absolute maximum of 100. Company filters can reduce the effective page size to 5 or 20; see Item Caps below.

For searches without company filters, the retrieval window is 1000 jobs: page * size must be less than 1000. The page number is zero-based.

sizeValid page rangeFirst page outside the window
1000-910
200-4950
100-99100
10-9991000

The last page can contain fewer jobs than requested. For example, page=12, size=80 starts at job 960 and can return up to 40 jobs. Narrow the search with filters to retrieve a different result set beyond the window; the Actor does not change the requested page or paginate automatically.

The input schema checks page and size individually. It cannot pre-validate their combination: page=10, size=100 passes the individual bounds but is rejected after a run starts, so the run can still finish as FAILED.

Item Caps

The maximum number of retrievable jobs depends on the query shape:

Query shapeMax itemsEffective max sizeOver-size behavior
No company filter1000100Validation error; not silently capped
Company filter plus another keyword or filter (including collar_type)2020Silent cap with capping metadata
Company filter only55Silent cap with capping metadata

A company filter means company_name, company_domain, or a company field referenced inside what. Another keyword or filter means anything in what other than company_*, or a value in fields such as title, category, sub_category, industry, posted, salary, employment_type, or seniority where available on this Actor.

When a company-filtered request asks for size greater than the effective cap, the API returns up to the capped number of results instead of erroring. The response metadata includes:

  • size_requested - the original requested size
  • size_capped_by - "company" for the 5-item cap or "company|keywords" for the 20-item cap

On uncapped responses, size_requested and size_capped_by are not present.

No-company-filter requests are not silently capped. If the request exceeds the 1000-item retrieval window, the API can return 400 Item limit reached. Maximum of 1000 items can be retrieved.

Free-Text Query Limits

These limits apply to each available user-entered field and are enforced before the Actor starts.

InputMaximum charactersMaximum operator characters
what50020
where50020

The operator-character limit counts ?, +, pipe, and @ together within each input. Field-targeted expressions must name supported fields explicitly; wildcard and exclusion field selectors are not allowed. Longer searches should be split into separate requests. Remaining backend syntax and safety checks can still reject an expression after the run starts.

The current JobsIndex API accepts up to 700 characters per effective query parameter. The smaller limits above, where applicable, and the 20-operator-character guard are Actor-side limits, not a claim that the API rejects every longer expression.

Field Validation

Apify validates the input schema before creating a run, including requests made directly through the API. A schema violation returns HTTP 400 with error.type = invalid-input; no run is created. Send only the input parameters listed for this Actor. API clients should handle this response when starting the Actor; there is no run ID to poll or run error file to fetch.

InputAccepted values / limits
pageInteger 0-999; the usable maximum also depends on size and query shape.
sizeInteger 1-100; company capping remains upstream.
company_domainA domain name only, e.g. example.com; 3-100 raw input characters. No protocol, path, port, or internal spaces. The API trims surrounding ASCII whitespace.
postedRecommended windows: 1d, 1w, 1m, 1y, or a real calendar date (YYYY, YYYY-MM, YYYY-MM-DD). Use 2-10 raw input characters. Surrounding ASCII whitespace is trimmed after the raw length check. Relative amounts use 1-4 digits without leading zeros.
salary2-30 raw input characters. 1-9 digits plus h, d, w, m, or y; a range needs units on both ends, e.g. 20h-30h. Surrounding ASCII whitespace is trimmed. Decimals and currency prefixes are not accepted.
employment_type2-50 raw input characters in total. Comma-separated values; 1-31 characters per item after trimming surrounding spaces. No empty items.
seniority2-50 raw input characters in total. Comma-separated values; 1-31 characters per item after trimming surrounding spaces. No empty items.
remoteremote, on-site, hybrid, or an empty string for no filter.
collar_typeHealthcare, White, Blue, or an empty string for no filter. Values are case-sensitive. Blank or omitted values are not sent to JobsIndex. This standalone filter does not rewrite what or where.
idOne numeric JobsIndex job ID; ID lists are not accepted. A correctly formatted but missing ID can still produce an upstream error.
Other text fieldsRaw input character ranges: country (2-60), region (2-80), city (2-100), postal_code (3-15), metro_area (2-100), title (2-200), company_name (2-150), category (2-100), sub_category (2-100), industry (2-100). Empty optional inputs remain allowed.

Empty optional text fields are allowed and are omitted from the upstream request. Raw input length means the decoded string including surrounding whitespace, before API trimming, not URL-encoded bytes. The schema checks preliminary formats, list structure, and lengths, not whether a matching location, employer, role, or job exists. The API retains its detailed character checks, including permitted Unicode characters in list values. A valid search with no matching jobs succeeds with an empty dataset.

Query-dependent pagination, combined filters, and other backend-only checks remain upstream or runtime checks. If they reject a request after a run starts, the run can still finish as FAILED. Technical errors are not reported as successful searches.

Example: filter results by collar type.

{
"collar_type": "White",
"size": 5
}

ID Lookup Shortcut

When id is provided, the search query is bypassed and the API looks up one job record. Use a single numeric JobsIndex job ID, not a comma-separated list. Leave collar_type empty for ID lookups. Combining an ID with a nonempty collar type is rejected after the run starts, before contacting JobsIndex. A well-formed ID that does not exist can still return 404 Job not found after the run starts.

Output

Job records include collar_type when provided by JobsIndex. The value can be Healthcare, White, Blue, n/a (not classified), an empty string, or null if unavailable. Only Healthcare, White, and Blue can be used to filter results.

Each run stores job records in the default Apify dataset. Raw data (all fields) shows the public fields returned by this Actor.

Example dataset item:

{
"id": "15131474020159014052",
"title": "Software Engineer",
"company_name": "Nuro",
"company_domain": "nuro.ai",
"collar_type": "White",
"category": "Information Technology",
"sub_category": "Software Developer",
"country": "United States",
"region": "California",
"city": "Mountain View",
"salary_value": null,
"salary_currency": null,
"salary_unit": null,
"employment_type": "Full-Time",
"remote": "n/a",
"posted": "2026-06-22",
"url_apply": "https://boards.greenhouse.io/embed/job_app"
}

Field availability depends on the source job posting.