Legacy Knowledge Base
Published Sep. 10, 2025

What filtering syntax to use in headless API for filtering for those entries that do not belong to any categories?

Written By

Sorin Pop

How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!

While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack" publication program, made available for informational purposes. Articles in this program were published without a requirement for independent editing or verification and are provided"as is" without guarantee.

Before using any information from this article, independently verify its suitability for your situation and project.

Issue

  • I am using the API GET /v1.0/asset-libraries/{assetLibraryId}/content-elements, but the question might be relevant for other endpoints as well
  • according to https://learn.liferay.com/w/dxp/low-code/objects/understanding-object-integrations/using-custom-object-apis/object-api-basics , at the time of writing this article (August 2025) there is this example syntax given for saying something like "give me back those entries that belong to this or that category"
taxonomyCategoryIds/any(k:k in (1234,5678))

However, there is no example for what syntax should be used if I want to say "give me back those entries that do not belong to any category". How can I do that?

 

Environment

  • QR

Resolution

  • syntax
 not taxonomyCategoryIds/any(k:k ne null)

 

should work. Please also make sure that you use public vocabularies, it might not work otherwise.

  • for object API's (currently), the syntax 
not taxonomyCategoryIds/any()

 

should also work.

 

 

Did this article resolve your issue ?

Legacy Knowledge Base