Feature Request

It would be great to be able to publish our articles as an MCP server, so AIs can access them.

We are migrating from another platform to Doc360. All articles have been added to Doc360 with a default setting for links in articles defined to External links and Open in new tab. However, for SEO purposes, we need to set External links to Article and deselect the Open in new tab option. As we have thousands of links in the help desk, we need a way to do this programmatically and automate the process.

I want an API that lets us View and access article feedback comments Lets us set statuses for the feedback So that I can Use an integration to put feedback into JIRA as a task (easier to assign, track, and collaborate) Use the same integration to update the status of the feedback when the work has been completed

For reader self registration there doesnt seem to be a way to add an allowed domain via API. Would be key. THank you

Currently there are no API endpoints to access analytics, which is vital functionality to extend reporting functionality and integrate it the insights into other tools.

Currently, managing self-registered readers and their group assignments cannot be done programmatically through the Customer API. This forces manual administration in the portal, which is inefficient and error-prone for organizations with a large number of users. Proposed Solution: Extend the Customer API to include endpoints for: Managing self-registration settings (enable/disable, allowed domains). Automatically assigning readers to specific groups upon registration via API configuration. Programmatically listing, adding, and removing readers from reader groups. This enables seamless user lifecycle management, allows for integration with external identity systems, and significantly reduces the manual overhead of maintaining readers and their permissions at scale.

In the API documentation editor, when adding a text block between endpoints (using the “+” symbol), the formatting options are currently limited. There is no direct option to insert a table, and pasting tables from other editors often breaks formatting and layout. Customers frequently need to include structured data, comparisons, and parameter references inside these text blocks. Since only basic formatting (bold, italics, underline, links, images, and code view) is available, creating properly formatted content becomes difficult and time-consuming. A direct “Insert Table” option inside the API documentation text block - along with additional formatting options similar to the regular documentation editor - would greatly improve usability and consistency, removing the need for workarounds and manual code adjustments.

When we export a list of our workspaces/categories/articles using the API, the "article status" column reports a number rather than the status label (i.e. published, draft, etc).

we extract articles via the api, some articles have a conditional access block, we now only see the uuid of the conditional access block, we would like to map this uuid with the logical name of the block. For example getting this out of the api would be helpful

One of our customers has asked if there are any plans to make Eddy AI work at the project level, instead of being limited to the workspace level. Their use case is that they want to integrate Eddy AI into their application with thier own custom chatbot. Since their documentation is spread across four workspaces, they would currently need to manage four separate custom chatbots to achieve this. A project-level endpoint would simplify the setup significantly and reduce maintenance overhead.