API problem detail
Invalid Filter Property
Description
Through the Experience API, a filter on a property that is not filterable for the endpoint is normally
refused by the gateway as 400 with the generic
Bad Request type and the title
Invalid Filter, and the detail names the property.
This type is a downstream fallback: it appears only when a property name the gateway allows is not found on the internal model that answers the request. The detail names the property.
Experience API error bodies also carry errorCode, resolution, and
traceId. Branch on errorCode, not on title or
detail; see fields on every error.
How to resolve
Filter only on the endpoint's documented response fields (account and routing numbers are never
filterable). Property names are matched against the response shape, not your internal names. Fix the
filter before retrying: the same filter is always refused.