Implement RecurringTransaction CRUD API endpoints #19

Open
opened 2026-10-30 21:00:34 -06:00 by west · 0 comments
Owner

📋 CRUD HTTP endpoints for recurring transactions on the server.

🎯 Acceptance Criteria:

  • GET /recurring — list active recurring transactions (with optional filters)
  • POST /recurring — create a new recurring transaction
  • PUT /recurring/{id} — update (including enable/disable via isActive)
  • DELETE /recurring/{id} — soft delete
  • On create/update/delete: automatically appends action to sync_outbox
  • Proper validation for frequency, amount, dates

📝 Notes: The active list endpoint is the most commonly used — optimize for it.

📋 **CRUD HTTP endpoints for recurring transactions on the server.** 🎯 **Acceptance Criteria:** - [ ] GET /recurring — list active recurring transactions (with optional filters) - [ ] POST /recurring — create a new recurring transaction - [ ] PUT /recurring/{id} — update (including enable/disable via isActive) - [ ] DELETE /recurring/{id} — soft delete - [ ] On create/update/delete: automatically appends action to sync_outbox - [ ] Proper validation for frequency, amount, dates 📝 **Notes:** The active list endpoint is the most commonly used — optimize for it.
Sign in to join this conversation.
No description provided.