Implement OpenAPI Schema Validation

[fejilaup-cloud]

The API server has no OpenAPI schema validation. Clients cannot auto-generate SDKs, and there is no contract between server and client.\n\n## Tasks:\n- Add OpenAPI 3.0 schema to docs/openapi.yaml\n- Implement schema validation middleware in main.rs\n- Add tests for schema compliance\n- Generate TypeScript client from schema\n\nLabels: enhancement, api-server\nPriority: High

[johnsmccain]

@johnsmccain has applied to work on this issue as part of the Stellar Wave Program's 4th wave.

I’m a full-stack developer experienced with API design and contract-first architecture, and I’d introduce a proper OpenAPI 3.0 contract layer to make the API fully self-describing and enforceable. I’d start by defining the complete API surface in docs/openapi.yaml, ensuring all endpoints, request/response schemas, and error models are explicitly documented for SDK generation and client consistency. Then I’d integrate schema validation middleware in main.rs to validate incoming requests against the OpenAPI spec at runtime, rejecting non-compliant payloads early to enforce contract safety. I’d add tests to verify schema compliance across key endpoints, including both valid and invalid payload cases to ensure strict adherence. Finally, I’d generate a TypeScript client from the schema to enable type-safe consumption on the frontend, establishing a single source of truth between server and client and eliminating drift between implementations.

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

[temma02]

@temma02 has applied to work on this issue as part of the Stellar Wave Program's 4th wave.

Hello team,
I'd like to take on this task and feel free to assign it to me.
Looking forward to getting started!

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

[drips-wave]

Congratulations, @temma02! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on April 29, 2026.

🧑‍💻 @temma02: 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 🌊

[drips-wave]

This issue has been completed by @temma02 as part of the Stellar Wave Program's 4th Wave 🥳

😎 @temma02: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.