Using the API to specify filters and tags with & (ampersand) in them

I noticed that all API requests to filter my search based on a filter which contains ‘&’ fail to give results.

The solution was to escape the & into &

If you are using the REST endpoint, this then needs to be URL Encoded so for example:
Search filter to show category: “Dogs & Cats
Filter parameter becomes: Category = 'Dogs & Cats'
Raw URL query becomes: filters[category]=Dogs %26amp%3B Cats

Hey there,

If the & in the URL request filter value is being encoded as %26 you should be right as rain.

Would it be possible to provide an active example to where the request transformation and error is taking place? We’d be happy to take a closer look.