Feature Request

We're migrating our API documentation to Document 360 now the API documentation add-on is available, so we purchased a sandbox so we can safely test the migration and enhance our reader SSO integration to control access to the API pages... But now the CSM tells me the sandbox doesn't support the API Documentation add-on?!! Why?! Please add this ASAP. I don't understand why this would be a limitation of the sandbox environment, isn't the sandbox just a replica project with a cheaper licence for testing?

Hello, A feature that would be really useful is to allow API Reference to link existing Articles. I see there is a way in Articles to link any API Spec Endpoint but no the other way around.

Please provide a recycle bin in the API section so that manually created articles can be recovered if they are deleted

If a company want to use both the KB AND the new API functionality, it seems users are unable to search for results in both places at the same time. This is very unfortunate behavior because it puts the burden of knowing where the information is on the user. For the API tool to be fully effective, it must be part of the global search for users.

There is no backup of API content – if it's deleted by mistake, it’s gone forever.

The "Import the API reference spec file" API requires us to define a publicly accessible link when importing an API reference, but our API spec contains data we don't want to publish publicly. We would like to send the API spec file directly to the Doc360 REST API.

I have an API that requires documentation and would like to upload a swagger/open api spec file to generate the API Documentation. An example of this feature is available on Read Me. https://readme.com/documentation

It will be great if we can add an API Explorer for API documentation. That way, we can provide the users to try the API while looking at the API documentation. Something like this: https://docs.scale.com/reference#callbacks Try IT button