What is the problem you are trying to solve?
Liferay Headless APIs use URL query parameters (such as filter) for complex searches. As filters become more advanced with nested conditions, relationship queries, sorting, and pagination, URLs become difficult to read, generate, and maintain. Many developers end up creating custom POST /search endpoints, even though the operation is read-only.
What is your project about? (e. g. Intranet, Partner Portal, Enterprise Website, etc)
Enterprise applications using Liferay Headless APIs, Custom Objects, and modern frontend frameworks (React, Angular, Vue) with advanced search and filtering requirements.
What is your proposed solution? (optional)
Consider adding experimental support for HTTP QUERY (RFC 10008) in the future, once ecosystem support is mature. This would allow clients to send structured JSON search criteria in a request body while keeping the operation safe and read-only, without replacing existing GET endpoints.
This could improve developer experience for complex Object searches, low-code applications, and AI-generated queries while maintaining backward compatibility with existing APIs.