API DOCUMENTATION / JOB FILTERS

Job filters

See how source-supported text, location, posting, date, pay, and representation options shape a jobs request.

Source-supported list filters

Query fieldsType, default, or rangeApplied behavior
q, title, descriptionText; 1–200 characters.Phrase-style matching over job title and/or description. q does not search company or location.
title_advanced, description_advancedValidated Boolean search expression.Advanced text matching against the named field.
company, company_idText substring; canonical lowercase UUID.Matches employer text or canonical company identity.
location, city, state, countryText; country accepts a two-letter code.Location predicates. Combined conditions apply to a matching indexed location row.
work_arrangement or remote_typeEnum: remote, hybrid, in_person.Aliases cannot be combined.
employment_type, source, exclude_source, source_type, source_classText or source-class enum; exclude up to 10 sources.Match or exclude permitted posting sources and source classes.
job_id, posting_id, source_posting_id, posting_statusCanonical lowercase job UUID; text posting IDs; status enum.Restrict results by matching job/posting identity and listed status.
currentness or activeCSV enum defaults to current; boolean alias is lowercase true/false.active=true maps to current; false maps to not_current.
posted_since/published_since, posted_untilRFC 3339 timestamp or YYYY-MM-DD date.Publisher date range. The two “since” aliases cannot be combined.
first_seen_since/until, updated_since/until, curated_since/untilRFC 3339 timestamp or YYYY-MM-DD date.Job timestamp ranges.
stale, company_linked, has_description/location/pay/posting_url/application_urlLowercase boolean.Match published presence and status fields.
pay_currency, pay_min, pay_maxSupported ISO 4217 code; amount 0–1,000,000,000.Match known pay values; minimum cannot exceed maximum.
last_fetch_since/until, application_check, application_check_sinceRFC 3339 timestamp; application-check enum.Filter by posting fetch and application-check fields.

Representation options

include=company adds a company object or null to list results when the company projection can be resolved. include=source_data adds stored source payload and rights to postings. description_format=text is the default; description_format=html returns an unavailable error until confirmed source HTML is provided. The count route rejects include and description_format.

Strict request parsing

Unknown or repeated query fields are rejected. Boolean values use lowercase true or false; list-valued fields are comma-separated with no duplicates. work_arrangement and remote_type cannot be combined, nor can active with currentness or posted_since with published_since.

Validation and representation options

Parameter groupType and accepted valuesExecution
currentnessUnique comma-separated values: current, uncertain, not_current. No spaces or repeated values. Defaults to current.List and count.
activeLowercase boolean. true maps to current; false maps to not_current.Cannot be combined with currentness.
includeUnique comma-separated values: company, source_data.List adds company or source data when requested. Count rejects this parameter.
description_formattext or html. Defaults to text.List and detail HTML requests can return unavailable until confirmed source HTML is available. Count rejects it.
Pay boundsNonnegative decimal from 0 to 1,000,000,000; at most two decimals; pay_min <= pay_max. pay_currency is a supported ISO 4217 code.List and count use the shared public-jobs filter builder. A pay range uses known pay values; no currency conversion or pay-period filter is applied.
Dates and aliasesRFC 3339 timestamps require a timezone. posted_since and published_since are aliases; only one may appear.Both. work_arrangement and remote_type are also mutually exclusive aliases.

Unknown and repeated query keys are rejected. Text filters accept 1–200 characters; booleans are lowercase true or false.

Continue in the reference

Check related request behavior before you build.

View route status and methods Discuss API requirements
All API documentation