docs: update comprehensive API documentation and project guides
This commit updates all documentation files throughout the project: - Updated IMPLEMENTATION_PLAN.md with new implementation details - Updated PROJECT_GUIDELINES.md with coding standards and practices - Updated README.md with current project information - Updated SCREENSHOT_AUTOMATION.md with new automation details - Added TEST_DATA.md with test fixtures data - Updated cover_image_serving_plan.md with static URL patterns Documentation API updates: - Updated API reference documentation for all endpoints including: - Authentication (login, logout, register, refresh_token) - Book matching (auto_link, bulk_link, link_book, search) - Collections (CRUD operations, shelf mappings, auto-assign rules) - Conflicts (bulk operations, resolve/dismiss) - Devices (registration, approval, shelf management) - Highlights (create, update, delete, get) - Kobo sync (bookmark, markup, initialization, sync) - KOReader sync (library, metadata, bookmarks, progress) - Libraries (CRUD, folders, media items, stats) - Media items (bulk operations, CRUD) - Notes (CRUD operations) - OPDS (acquisition, feeds, publication) - Progress (reading progress tracking) - Queue (device queue management) - Ratings (star ratings) - Scanner (watch mode, scan operations) - Sync protocols (Kobo, KOReader) - Users (profile, password, admin operations) - WebSocket protocols - Updated user guides (admin, dashboard, settings, sync) - Updated device setup guides (Kobo, KOReader) - Updated developer guides (testing, contributing, operations) - Updated scripts/README.md
This commit is contained in:
@@ -8,10 +8,10 @@ Authenticate with email and password.
|
||||
|
||||
## Request Body
|
||||
|
||||
| Field | Type | Required | Description |
|
||||
|--------|------|-----------|-------------|
|
||||
| login | string | Yes | User's email address or username |
|
||||
| password | string | Yes | User's password |
|
||||
| Field | Type | Required | Description |
|
||||
| -------- | ------ | -------- | -------------------------------- |
|
||||
| login | string | Yes | User's email address or username |
|
||||
| password | string | Yes | User's password |
|
||||
|
||||
### Example Request
|
||||
|
||||
@@ -42,6 +42,7 @@ Authenticate with email and password.
|
||||
```
|
||||
|
||||
**Set-Cookie Header**:
|
||||
|
||||
```
|
||||
Set-Cookie: token=eyJhbG...; Max-Age=604800; Path=/; HttpOnly
|
||||
```
|
||||
@@ -50,8 +51,8 @@ Set-Cookie: token=eyJhbG...; Max-Age=604800; Path=/; HttpOnly
|
||||
|
||||
## Error Responses
|
||||
|
||||
| Code | Description |
|
||||
|------|-------------|
|
||||
| 401 | Invalid email or password |
|
||||
| 400 | Missing required fields |
|
||||
| 429 | Too many login attempts |
|
||||
| Code | Description |
|
||||
| ---- | ------------------------- |
|
||||
| 401 | Invalid email or password |
|
||||
| 400 | Missing required fields |
|
||||
| 429 | Too many login attempts |
|
||||
|
||||
@@ -8,9 +8,9 @@ Invalidate the current JWT token.
|
||||
|
||||
## Request Headers
|
||||
|
||||
| Header | Type | Required | Description |
|
||||
|--------|------|-----------|-------------|
|
||||
| Authorization | string | Yes | Bearer token (e.g., `Bearer eyJhbG...`) |
|
||||
| Header | Type | Required | Description |
|
||||
| ------------- | ------ | -------- | --------------------------------------- |
|
||||
| Authorization | string | Yes | Bearer token (e.g., `Bearer eyJhbG...`) |
|
||||
|
||||
### Example Request
|
||||
|
||||
@@ -25,7 +25,7 @@ No response body.
|
||||
|
||||
## Error Responses
|
||||
|
||||
| Code | Description |
|
||||
|------|-------------|
|
||||
| 401 | Invalid or expired token |
|
||||
| 403 | Token already invalidated |
|
||||
| Code | Description |
|
||||
| ---- | ------------------------- |
|
||||
| 401 | Invalid or expired token |
|
||||
| 403 | Token already invalidated |
|
||||
|
||||
@@ -42,6 +42,7 @@ When a user registers or logs in:
|
||||
4. Server returns JSON response with both tokens and user profile
|
||||
|
||||
**Request**:
|
||||
|
||||
```json
|
||||
POST /api/auth/login
|
||||
{
|
||||
@@ -51,6 +52,7 @@ POST /api/auth/login
|
||||
```
|
||||
|
||||
**Response**:
|
||||
|
||||
```json
|
||||
{
|
||||
"token": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...",
|
||||
@@ -67,6 +69,7 @@ POST /api/auth/login
|
||||
```
|
||||
|
||||
**Set-Cookie Header**:
|
||||
|
||||
```
|
||||
Set-Cookie: token=eyJhbG...; Max-Age=604800; Path=/; HttpOnly
|
||||
```
|
||||
@@ -94,6 +97,7 @@ POST /api/auth/refresh
|
||||
```
|
||||
|
||||
**Response**:
|
||||
|
||||
```json
|
||||
{
|
||||
"access_token": "new-jwt-token",
|
||||
@@ -135,6 +139,7 @@ When an API call receives a 401 Unauthorized response:
|
||||
```
|
||||
|
||||
The frontend toast.js interceptor:
|
||||
|
||||
1. Clears invalid tokens from localStorage
|
||||
2. Shows an error toast notification
|
||||
3. Allows user to re-authenticate
|
||||
@@ -149,10 +154,12 @@ The frontend toast.js interceptor:
|
||||
## Token Storage Recommendations
|
||||
|
||||
### Browser Applications
|
||||
|
||||
- **Backend**: Automatically manages HTTP-only cookie
|
||||
- **Frontend**: Store tokens in localStorage for API calls
|
||||
|
||||
### Mobile Applications
|
||||
|
||||
- Store access token in secure storage (Keychain/Keystore)
|
||||
- Store refresh token in secure storage
|
||||
- Handle 401 responses by prompting user to re-authenticate
|
||||
@@ -160,6 +167,7 @@ The frontend toast.js interceptor:
|
||||
## Constants Reference
|
||||
|
||||
All session durations use constants defined in:
|
||||
|
||||
- `internal/handlers/auth.go` - SessionDuration, SessionDurationSec
|
||||
- `internal/handlers/refresh_token.go` - SessionDurationSec (mirrored)
|
||||
|
||||
|
||||
@@ -8,9 +8,9 @@ Obtain a new JWT access token using a refresh token.
|
||||
|
||||
## Request Body
|
||||
|
||||
| Field | Type | Required | Description |
|
||||
|--------|------|-----------|-------------|
|
||||
| refresh_token | string | Yes | Valid refresh token (UUID) |
|
||||
| Field | Type | Required | Description |
|
||||
| ------------- | ------ | -------- | -------------------------- |
|
||||
| refresh_token | string | Yes | Valid refresh token (UUID) |
|
||||
|
||||
### Example Request
|
||||
|
||||
@@ -36,7 +36,7 @@ The new access token is valid for 7 days from the time of refresh.
|
||||
|
||||
## Error Responses
|
||||
|
||||
| Code | Description |
|
||||
|------|-------------|
|
||||
| 401 | Invalid or expired refresh token |
|
||||
| 400 | Missing refresh token or invalid format |
|
||||
| Code | Description |
|
||||
| ---- | --------------------------------------- |
|
||||
| 401 | Invalid or expired refresh token |
|
||||
| 400 | Missing refresh token or invalid format |
|
||||
|
||||
@@ -8,13 +8,13 @@ Create a new user account.
|
||||
|
||||
## Request Body
|
||||
|
||||
| Field | Type | Required | Description |
|
||||
|--------|------|-----------|-------------|
|
||||
| email | string | Yes | User's email address |
|
||||
| username | string | Yes | Desired username (3-50 chars) |
|
||||
| password | string | Yes | Password (min 8 chars, must meet complexity requirements) |
|
||||
| first_name | string | No | User's first name |
|
||||
| last_name | string | No | User's last name |
|
||||
| Field | Type | Required | Description |
|
||||
| ---------- | ------ | -------- | --------------------------------------------------------- |
|
||||
| email | string | Yes | User's email address |
|
||||
| username | string | Yes | Desired username (3-50 chars) |
|
||||
| password | string | Yes | Password (min 8 chars, must meet complexity requirements) |
|
||||
| first_name | string | No | User's first name |
|
||||
| last_name | string | No | User's last name |
|
||||
|
||||
### Example Request
|
||||
|
||||
@@ -50,6 +50,7 @@ Create a new user account.
|
||||
```
|
||||
|
||||
**Set-Cookie Header**:
|
||||
|
||||
```
|
||||
Set-Cookie: token=eyJhbG...; Max-Age=604800; Path=/; HttpOnly
|
||||
```
|
||||
@@ -60,7 +61,7 @@ Set-Cookie: token=eyJhbG...; Max-Age=604800; Path=/; HttpOnly
|
||||
|
||||
## Error Responses
|
||||
|
||||
| Code | Description |
|
||||
|------|-------------|
|
||||
| 400 | Invalid email format, weak password, or missing fields |
|
||||
| 409 | Email or username already exists |
|
||||
| Code | Description |
|
||||
| ---- | ------------------------------------------------------ |
|
||||
| 400 | Invalid email format, weak password, or missing fields |
|
||||
| 409 | Email or username already exists |
|
||||
|
||||
Reference in New Issue
Block a user