docs: add comprehensive API endpoint documentation #21
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
This PR adds complete API reference documentation that was previously missing from the project.
What's New
New File:
docs/API_ENDPOINTS.md(872 lines)A comprehensive API reference covering the entire application surface:
📡 REST API Endpoints (2)
POST /api/summarize
/api/auth/[...all]
⚡ Server Actions (11)
Authentication (3)
signIn()- Email/password authenticationsignUp()- User registrationsignOut()- Session terminationTodos (6)
getAllTodos()- Fetch user's todos with categoriesgetTodoById()- Fetch single todocreateTodoAction()- Create with optional R2 image uploadupdateTodoAction()- Full todo updateupdateTodoFieldAction()- Partial update (optimized)deleteTodoAction()- Delete todoCategories (2)
getAllCategories()- Fetch user's categoriescreateCategory()- Create new category📚 Additional Documentation
Authentication Details
getCurrentUser,requireAuth,isAuthenticated,getSession)Data Models
Error Handling
Development Patterns
What Each Entry Includes
For every endpoint/action, the documentation provides:
Why This Matters
Before: Developers had to read source code to understand the API
After: Complete reference for building features or integrations
This documentation:
Example Documentation Quality
Here's a sample entry structure:
Impact
This PR fills a major documentation gap in the project. Developers can now:
🤖 Generated with Claude Code