Reader Group Filter Support in Project Version Articles API
under review
Kesavan M
Ability to filter articles returned from the Project Version Articles API endpoint based on reader group ID. This would ensure that only content permitted for a specific reader group is fetched and displayed in external applications such as chatbots. The current multi-step workaround using separate endpoints is complex and not optimal for their use case. Adding a reader group parameter directly to the endpoint would provide a cleaner and more efficient solution. This enhancement is especially important for scenarios involving multiple reader groups with dynamic content access control.
Log In
Z
Zaffre blue Minnow
Hi,
Thanks for looking into this.
Please find the details below:
Number of reader groups - 2 to 3
Expected API call volume - We have a daily process to list the articles and check for updates so project-version-articles would be once per reader group per day
Let us know if any additional information is needed from our end.
Thanks,
Mohit
Kesavan M
++Zaffre blue Minnow
Mohamed Shakheen
marked this post as
under review
Mohamed Shakheen
Hi Particular Beetle Kesavan
Thank you for sharing this requirement in detail - this is a well-articulated use case, particularly for external integrations like chatbots that rely on context-aware content delivery.
We understand the need to filter articles from the Project Version Articles API based on reader group access, and how the current multi-step approach using multiple endpoints can add complexity to your implementation.
At this stage, we would like to further validate this requirement to better understand its applicability across different use cases and ensure alignment with our existing permission architecture. Specifically, we’ll be looking into:
- The frequency and scale of reader group–based filtering in API-driven integrations
- The performance implications of introducing access control filters at the API level
- How this fits within the current access control and caching mechanisms
This validation will help us determine the most effective and scalable way to address the need, without impacting system performance or existing workflows.
If you can share additional context - such as the number of reader groups, expected API call volume, or how frequently content access changes - it would help us assess this more effectively.
We’ll keep you informed as we progress through this validation.