Legacy Knowledge Base
Published Sep. 10, 2025

Not able to get results for internal categories when fetching via APIs

Written By

Madhusudan Sharma

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

  • Not getting similar results from Headless APIs when filtering content by internal categories. However, everything works fine with Public categories.
  • The following are the steps:
    1. Create an Asset Library, Vocabulary (internal), Category, Folder, and Web Contents
    2. Assign the internal Category to a Web Content.
    3. Use the Headless API endpoint /o/headless-delivery/v1.0/structured-content-folders/{folderId}/structured-contents to retrieve content.
    4. Apply the filter criteria taxonomyCategoryIds/any(t:t eq {category_id}) with the internal Category ID.

    Expected Behavior: Information about the internal categories should be returned when the filter criteria is applied.
    Observed Behavior: Information about the internal categories is not coming when the filter criteria is applied.

Environment

  • Liferay DXP 7.4

Resolution

  • The reported behavior is the Product's current limitation because the indexing of internal and external categories is currently done independently.
  • Additionally, due to its complexity and dependencies on the multiple components, it would not be possible to provide a fix to resolve this.
  • As a workaround, without making categories public, it can be possible keeping the internal category-applied web contents in the same folder and keep them in a different folder. In conclusion, avoid filtering and fetch the data directly.

Additional Information

Did this article resolve your issue ?

Legacy Knowledge Base