400

API problem detail

Filter Parsing Problem

Description

Through the Experience API, a filter that is not valid JSON or is not shaped as an object of property-name arrays is refused by the gateway as 400 with the generic Bad Request type and the title Invalid Filter. Collection endpoints that accept the filter but cannot apply it report a Filter Problem.

This type is a downstream fallback that internal services use for the same parsing failures.

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

Serialize the filter as documented: a JSON object keyed by property name, each holding an array of operator objects, URL-encoded before sending. Fix the filter before retrying: the same filter is always refused.
Back to all problem details