apache
Suggestion to open REST API documentation to support secondary development
Is your feature request related to a problem? Please describe
None.
Describe the solution you'd like
I would like to suggest opening up REST API documentation for the answer project to allow secondary development by third-party developers and partners.
Providing API documentation could enable the creation of integrations and add-on applications that enhance the capabilities of answer. Some ideas include mobile apps, browser extensions, or import/export tools for answer content.
Opening the API with thorough documentation and examples would make it easier for external developers to build on top of answer in innovative ways. It would also demonstrate an openness and willingness to work with the developer community.
I'm happy to discuss API capabilities that would be most useful for integrations with the answer team. Please consider opening access to read and write APIs to grow an ecosystem around the product.
Describe alternatives you've considered
Explore API according to source code and browser console, but this is not stable.
@allinprogram Answer uses swagger to output API documentation, and if you run Answer you can access the documentation via a path /swagger/index.html. Such as https://meta.answer.dev/swagger/index.html
@LinkinStars Great, this is exciting. I looked through the official documents for a long time, but I didn't see this. Thank you for your guidance. I will close this issue and explore the api documentation.