Filter reference

One filter object is used in three places: search_jobs takes it as filters, save_search takes it as prefilter, and check_prefilter validates one and tells you how many postings it would catch. This page is that language.

The five value shapes

Each field has a type, and the type decides the envelope its value takes. Text is the odd one out and worth reading twice: the operator IS the key, and there is no operator field at all.

text — the operator is the key; give one or more of them

Operators: all_words, any_words, exact_phrase, none_words

{
  "<field>": {
    "all_words": "python scraper",
    "none_words": "wordpress"
  }
}

select — {"operator": , "values": [, …]}

Operators: equals, equals_all, not_equals, not_equals_any

{
  "<field>": {
    "operator": "equals",
    "values": [
      "<one of options>"
    ]
  }
}

numeric — {"operator": , "value1": ""} — "between" also needs value2

Operators: between, equals, greater_than, greater_than_or_equals, less_than, less_than_or_equals

{
  "<field>": {
    "operator": "greater_than",
    "value1": "1000"
  }
}

boolean — {"value": "Yes"|"No"} — no operator key

{
  "<field>": {
    "value": "Yes"
  }
}

date — {"operator": , "date1": "YYYY-MM-DD"} — "between" also needs date2

Operators: after, before, between, equals

{
  "<field>": {
    "operator": "after",
    "date1": "2026-01-01"
  }
}

Conventions

Three rules that no single field entry could tell you, and that produce refusals which make no sense until you know them.

• type names — text,numeric,select,boolean,date

• numbers are strings — numeric values go in as STRINGS — value1: "1000", not 1000. This is the v1 filter format the saved-search engine reads, and a real number is refused.

• booleans are yes no — boolean values are the strings "Yes" and "No", not true and false, for the same reason.

• options are authoritative — where a field carries options, that list is what the validator accepts. A field's prose description comes from the source system and may name values this corpus does not hold — engagement_weeks and hourly_budget_type both do. Filter on options, never on the sentence.

• bounds are observed not enforced — min and max are the range currently present in the corpus, not a constraint. A filter outside them is accepted and matches nothing; check_prefilter warns when a clause cannot match.

Combining filters

Several fields in one object are ANDed. There is no OR across fields; to widen, loosen a clause rather than adding another. Within a text field, any_words is the OR.

{
  "_combined|title|description|skills": { "exact_phrase": "React Native" },
  "buyer_payment_verified": { "value": "Yes" },
  "total_spent": { "operator": "greater_than", "value1": "5000" }
}

Run it through check_prefilter before saving. It returns matched, and a filter that catches nothing looks exactly like a quiet market — a saved search built on one fires forever without telling you it was the filter. It also returns warnings when a clause cannot match at all, such as a numeric comparison outside the range the corpus holds.

Every field

Bounds are values observed in the corpus, not limits — a filter outside them is valid and matches nothing.