Implement Transaction CRUD API endpoints #18

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

📋 CRUD HTTP endpoints for transactions on the server.

🎯 Acceptance Criteria:

  • GET /transactions — list with query params: date_range, tags, type, source_id
  • POST /transactions — create a new transaction, returns 201
  • PUT /transactions/{id} — update a transaction
  • DELETE /transactions/{id} — soft delete
  • On create/update/delete: automatically appends action to sync_outbox
  • All endpoints return proper error responses (404, 400, etc.)

📝 Notes: Each mutation must trigger a sync_outbox append with the entity payload.

📋 **CRUD HTTP endpoints for transactions on the server.** 🎯 **Acceptance Criteria:** - [ ] GET /transactions — list with query params: date_range, tags, type, source_id - [ ] POST /transactions — create a new transaction, returns 201 - [ ] PUT /transactions/{id} — update a transaction - [ ] DELETE /transactions/{id} — soft delete - [ ] On create/update/delete: automatically appends action to sync_outbox - [ ] All endpoints return proper error responses (404, 400, etc.) 📝 **Notes:** Each mutation must trigger a sync_outbox append with the entity payload.
Sign in to join this conversation.
No description provided.