Discussions
Displaying recursive data results from an API
My api response returns data with the following structure
Error submitting form after updating a page
When I update a Guide page, I get a message that says error submitting form. This happens after entering text and clicking the Save to Staging button. The page that I am working on is quite large with many tables. Do you have any ideas why I am getting this error and what I can do?
Is there a plan to support webhooks in OAS 3.1?
We'd love to be able to upload our webhooks specifications to ReadMe. Are there plans to support it? Any suggested alternatives in the meantime besides creating custom pages?
Moving conent around
Is it possible to make an existing page a subpage of another existing page?
How to recreate the reference getting started page?
I really like the Getting Started page here when you go to the API Reference:
Editor woes
It appears that legacy editor no longer saves content correctly (or sometimes at all)
Is it possible to make categories expandable?
Our left-hand navigation is getting quite long. Is it possible to make a category retractable and expandable so that users only see the category name until they choose to expand it?
Can I recover a documentation page within API Reference?
I see how to use Page History within Guides to recover content, but have found no way to recover a deleted documentation page with the API Reference section.
Feedback
Nothing worse than taking the time to type up a bunch of feedback only to realize the submit ideas forms is broken, so dropping it here instead:
API Conventions for /api-specification
GET /api-specification returns a collection instead of single api and there is no GET /api-specification/{id} call. I would expect an /api-specifications endpoint to exist and return a collection