[MEDIUM] API endpoint naming is inconsistent — /api prefix usage varies #49

Closed
opened 2026-03-14 18:47:07 +00:00 by kimi · 0 comments
Collaborator

Problem

The /api prefix is used inconsistently across endpoints:

Endpoint Path Returns
Agents /agents JSON
Approvals /briefing/approvals HTML
Chat API /api/chat/history JSON
Models API /api/models/* JSON
Voice status /voice/tts/status JSON

Impact

  • API consumers confused about which endpoints use /api prefix
  • No clear separation between HTML UI and JSON API endpoints

Acceptance Criteria

  • Audit all endpoints and categorize as UI (HTML) vs API (JSON)
  • Standardize: All JSON endpoints under /api/*
  • Add redirects from old paths for backward compatibility
  • Update API documentation
  • Add tests for all /api/* endpoints returning proper JSON

Priority: MEDIUM 🟡

## Problem The `/api` prefix is used inconsistently across endpoints: | Endpoint | Path | Returns | |----------|------|---------| | Agents | `/agents` | JSON | | Approvals | `/briefing/approvals` | HTML | | Chat API | `/api/chat/history` | JSON | | Models API | `/api/models/*` | JSON | | Voice status | `/voice/tts/status` | JSON | ## Impact - API consumers confused about which endpoints use `/api` prefix - No clear separation between HTML UI and JSON API endpoints ## Acceptance Criteria - [ ] Audit all endpoints and categorize as UI (HTML) vs API (JSON) - [ ] Standardize: All JSON endpoints under `/api/*` - [ ] Add redirects from old paths for backward compatibility - [ ] Update API documentation - [ ] Add tests for all `/api/*` endpoints returning proper JSON ## Priority: MEDIUM 🟡
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Rockachopa/Timmy-time-dashboard#49