Filter reference

Generated from the same registry the API validates requests against. Anything listed here is accepted; anything not listed returns 400.

How filters combine

• Values within one parameter are an OR. states=UT,CO means Utah or Colorado.
• Different parameters are ANDed. states=UT&assetClasses=Apartment%20Building means Utah and apartment buildings.
• propertyTypes, propertySubtypes and assetClasses are OR-joined with each other first, then ANDed with everything else. Selecting a type and an unrelated asset class gives you the union, not the intersection.
• A county or city narrows within the states you named rather than adding to them.

curl 'https://api.boardwalkai.com/api/v1/projects/search?states=UT&estimatedProjectValueMin=1000000' \
  -H 'Authorization: Bearer bwk_live_YOUR_KEY'

{
  "error": {
    "code": "invalid_filter",
    "message": "1 filter problem. No credits were charged.",
    "param": "estimatedProjectValueMin",
    "details": {
      "problems": [
        {
          "param": "estimatedProjectValueMin",
          "code": "unknown_parameter",
          "message": "Unknown parameter \"estimatedProjectValueMin\". Nothing was charged.",
          "details": []
        }
      ]
    },
    "docsUrl": "https://boardwalkai.com/docs/api/errors#invalid_filter",
    "requestId": "req_01K1QF3M0000EXAMPLE0001"
  }
}

Defaults that are applied for you

Two defaults change what a bare query returns, and both are disclosed in the response so you can assert on them rather than remember them:

The receipt

Every filtered response carries meta.appliedFilters — what actually ran after normalisation and name resolution — plus meta.appliedDefaults and meta.resolvedFrom. If you ever need to prove the API searched what you meant, diff those against what you sent.

Every filter