Publish a versioned OpenAPI spec for the public and authenticated routes

[robertocarlous]

Why
The backend has many routes and validation layers, but there is no single contract document for consumers. A generated or maintained OpenAPI spec would reduce integration friction.

Acceptance criteria

• Generate or maintain an OpenAPI document for the main HTTP surface.
• Include auth requirements and request/response examples.
• Make the spec available in docs and, if practical, as a build artifact.

[Macnelson9]

Hi team, I'd like to take on this issue.

I specialize in Rust development, smart contract engineering, and frontend development with Next.js, React, and TypeScript. My experience allows me to bridge on-chain functionality with intuitive user experiences, ensuring both technical correctness and usability.

I'll follow the existing codebase conventions, communicate progress clearly, and deliver a high-quality solution within the expected timeline.

Thank you for your consideration.

[Macnelson9]

Hi team, I'd like to take on this issue.

I specialize in Rust development, smart contract engineering, and frontend development with Next.js, React, and TypeScript. My experience allows me to bridge on-chain functionality with intuitive user experiences, ensuring both technical correctness and usability.

I'll follow the existing codebase conventions, communicate progress clearly, and deliver a high-quality solution within the expected timeline.

Thank you for your consideration.

[Elizabeth-dev270]

I enjoy solving software problems and have experience in backend development, APIs, OOP, and scalable application design.

[akindoyinabraham0-collab]

@akindoyinabraham0-collab has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

I will like to work on this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @akindoyinabraham0-collab to this issue.

[charliechinedu19-netizen]

@charliechinedu19-netizen has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hey gm, I’d really love to take on this task real quick

ℹ️ Repo Maintainers: To accept this application, review their application or assign @charliechinedu19-netizen to this issue.

[drips-wave]

Congratulations, @charliechinedu19-netizen! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @charliechinedu19-netizen: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox!

@charliechinedu19-netizen's PR #279 was approved and merged by @robertocarlous.

🏆 @charliechinedu19-netizen: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (35 total points). Track your full progress on GrantFox.

👏 Great work, @charliechinedu19-netizen! Keep contributing to Neurowealth.