Skip to content

Split API routes by domain with versioned namespacing #360

@Smartdevs17

Description

@Smartdevs17

Description

All API routes are in flat files. Refactor to versioned domain grouping for better organization and versioning strategy.

Acceptance Criteria

  • Versioned route prefixes (/v1/lending, /v1/oracle, /v1/governance)
  • Domain-based route file organization
  • Version migration middleware
  • Deprecation headers for old versions
  • OpenAPI spec per version
  • No breaking changes to existing clients

Technical Scope

  • api/src/routes/
  • api/src/app.ts
  • Edge: route conflict resolution, middleware duplication per version

Metadata

Metadata

Assignees

Labels

200-points200 point issueStellar WaveIssues in the Stellar wave programdrips-waveDrips Wave project taskhighHigh priority issue

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions