Feature Requests

Currently, the Helpjuice API uses a single API key for authentication, which grants full permissions (Super Administrator access). This approach does not follow the best practices of least privilege, as it requires customers to either grant full access or rely on workarounds like proxy servers to implement more secure, permission-based access. Requested Features: Ability to create API tokens with scoped permissions, allowing customers to restrict access to specific resources (e.g., read-only access, limit access to certain articles or categories). Option to configure custom API roles with granular access, following the principle of least privilege. More control over the permissions granted to API keys, ensuring they are tied to the access level of the associated user. This feature would significantly improve security and flexibility for customers using the Helpjuice API in more complex, secure integrations.

When retrieving an article via API v3, the groups_id field should be included in the response and contain an array of group IDs that have access to the private article.

Currently, we can't filter API v3 article results by archived. It would be useful if we could add an archived filter to the API V3 endpoint for articles. We also don't have the archived information in API v2 when retrieving the information in JSON and .xls formats. We should add it to these formats too.

Currently, we don't include the job title in the API response when retrieving users information. What is included "email", "name", "first_name", "last_name", "role_id", "created_at", "updated_at", "groups" etc. Consider adding this e.g. Trainer etc.

An API call that would retrieve a specified Article Version.

We will integrate HelpJuice with Cognigy Agent Assist to enhance our customer support operations. However, I know we will encountered a limitation that significantly impacts our implementation—the API call limit of 100. The HelpJuice API will be utilized extensively to search for answers within the Knowledge Base during both calls and chats. What is the process for requesting an increase in the API call limit? We would like to discuss options for a higher limit to accommodate our operational needs. Is there a way to manage or optimize API calls using JavaScript? Are there any best practices or example scripts available that could help us reduce the number of API calls? Do clients have access to HelpJuice JavaScript resources or repositories on GitHub that could assist in managing API call limits? If so, could you please provide the relevant links or documentation?