400

API problem detail

Filter Problem

Description

Most filter mistakes never reach this check. The API gateway validates every filter first and refuses it with 400, the generic Bad Request type, and the title Invalid Filter when the filter is not valid JSON, is not a JSON object, exceeds the size limits (64 KiB, 64 properties, 128 conditions, 512 values), names a property that is not filterable on that endpoint, or uses an operator name that is not supported. The detail names the offending part.

This type is the fallback for a filter that passed those checks but could not be applied, for example a property whose value is not an array of operator objects, an entry that is not an object, Match or Contains on a non-text property, or a comparison the property's type does not support. A missing operator or operand has its own type: No Filter Type Provided or No Filter Value Provided.

Response title: Dynamic Filtering Issue.

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

Send the filter as a URL-encoded JSON object keyed by property name, each holding an array of operator objects with a type and a value. Only the endpoint's documented response fields are filterable, and account and routing numbers never are. Prefer the endpoint's resource-specific query parameters where it offers them. Fix the filter before retrying: the same filter is always refused.
Back to all problem details