Context
The backend and currency API have no machine-readable API specification. API.md and FEE_SERVICE_API.md are hand-written and may drift from the implementation. External integrators have no way to generate client SDKs.
Expected Behavior
An OpenAPI 3.0 spec (openapi.yaml) should document all endpoints in both api/ and backend/ services, including request/response schemas, error codes, and authentication requirements.
Suggested Solution
Use zod-to-openapi or tsoa to generate the spec from TypeScript types, keeping it in sync automatically.
Acceptance Criteria
Priority: Medium
Context
The backend and currency API have no machine-readable API specification.
API.mdandFEE_SERVICE_API.mdare hand-written and may drift from the implementation. External integrators have no way to generate client SDKs.Expected Behavior
An OpenAPI 3.0 spec (
openapi.yaml) should document all endpoints in bothapi/andbackend/services, including request/response schemas, error codes, and authentication requirements.Suggested Solution
Use
zod-to-openapiortsoato generate the spec from TypeScript types, keeping it in sync automatically.Acceptance Criteria
openapi.yamlcovers all endpointsswagger-cli validateGET /api/docsserves Swagger UIPriority: Medium