Filter Reference

All filters are optional fields in the JSON request body of POST /v1/jobs/search. Filters combine with AND. Array filters ending in _or match any of their values; those ending in _not exclude their values.

Pagination & ordering

See pagination for how these interact.

Job title

Both match a case-insensitive substring of the title, so "engineer" also matches "Engineering Manager". job_title_not terms are excluded independently: a job is dropped if it contains any of them.

Description

The same case-insensitive substring match, run over the full posting text. Use it for a requirement that rarely appears in the title. When the term is in the skills lexicon, skills_or asks the same question against the extracted slugs and is the better filter.

Location

region_or is the precise way to ask for a state or province. job_location_or substring-matches the city or the region, so ["Ontario"] also returns jobs in Ontario, California, while ["CA-ON"] returns only the province.

work_arrangement_or is finer than remote, which answers false for hybrid and onsite alike and so cannot separate the two. Jobs whose arrangement we do not know never match it, which makes it stricter than the boolean rather than a drop-in replacement.

Posted date

discovered_at_gte tracks when we first saw a posting, not when it was posted. That makes it the one to poll with: pass the timestamp of your last run and you get everything new to the corpus since then, including older postings we discovered late, which a posted_at_gte window would miss.

Status

Search returns only active postings unless you ask otherwise. closed returns postings a recheck found gone, and any returns both. Closed jobs carry closed_at and closed_reason, which is closed, gone or stale.

Company

min_employee_count uses the exact headcount where we have one and otherwise the lower bound of the company's size band, since a "10,000+" company certainly has at least 10,000 people. max_employee_count uses the exact headcount only -- a band has no known upper bound, so those companies are excluded rather than wrongly included. Either way, narrowing by company size also narrows to companies whose size we know. To filter by industry instead, use isic_division_or, which classifies the hiring company under ISIC Rev.4.

Source

Accepted values: linkedin, indeed, ycombinator (aliases: yc, y combinator), workday, greenhouse, workable, smartrecruiters, ashby, lever, paylocity.

To get only ATS-direct postings, exclude the boards — this keeps working as new ATS sources are added:

{ "source_not": ["indeed", "linkedin"] }

Or pin an exact include list when you want only specific sources:

{ "source_or": ["workday", "greenhouse", "workable", "smartrecruiters", "ashby", "lever", "paylocity"] }

An unrecognized source is not an error: in source_or it matches nothing (the request returns zero jobs, so assert a non-zero count in integrations), and in source_not it excludes nothing.

Employer type

employer hires for itself, agency is a staffing or recruitment firm posting for a client, and broker is a job board republishing another company's listing.

Seniority

Responses report entry_level, mid_level, senior, director and executive. The filter accepts those and also entry, mid, lead, exec, internship and associate, matched case-insensitively. director and lead are the same bucket, which is why an individual-contributor principal can appear under director - use is_manager to tell them apart.

Most postings state no level at all - 31.2% carry one in the coverage sample - and job_seniority_or drops every unlabeled job. Set include_unlabeled_seniority: true to keep them.

Employment type

Underscored and unhyphenated spellings work too (full_time, fulltime), as do temp and intern. Postings whose type the source never stated match none of the values.

Occupation, industry & skills

Every posting is classified against international standards: the role into an ISCO-08 occupation unit group, the employer into an ISIC Rev.4 industry division, and the text against a curated skills lexicon.

By ID

Preview mode

With blur_company_data: true the response masks company, company_domain, url, source_url, description and every identifying field of company_object, empties hiring_team, and sets has_blurred_data: true. Job titles, locations, salary, dates and the result counts stay readable, and the call bills zero credits, so it is the way to size a search before paying for it.