Clean up API documentation files by removing Phase X references: Remove 'API Explorer will be inserted here in Phase X' placeholders from: - 70+ API endpoint documentation files - Authentication endpoints (login, logout, register, refresh) - User endpoints (profile, settings, password) - Device endpoints (registration, sync, shelves) - Library endpoints (CRUD, folders, visibility) - Media endpoints (items, progress, highlights, notes) - Admin endpoints (users, analytics) - Sync endpoints (Kobo, KOReader) - OPDS endpoints - Scanner endpoints - Queue endpoints These placeholders were from planning documents and have no meaning to API consumers. The documentation is now clean and ready for use.
38 lines
662 B
Markdown
38 lines
662 B
Markdown
# Refresh Token
|
|
|
|
Obtain a new JWT token using a refresh token.
|
|
|
|
**Endpoint**: `POST /api/auth/refresh`
|
|
**Auth**: Not required (uses refresh token)
|
|
**Content-Type**: `application/json`
|
|
|
|
## Request Body
|
|
|
|
| Field | Type | Required | Description |
|
|
|--------|------|-----------|-------------|
|
|
| refresh_token | string | Yes | Valid refresh token |
|
|
|
|
### Example Request
|
|
|
|
```json
|
|
{
|
|
"refresh_token": "d4f5g6h7..."
|
|
}
|
|
```
|
|
|
|
## Response (200 OK)
|
|
|
|
```json
|
|
{
|
|
"token": "new-jwt-token",
|
|
"refresh_token": "new-refresh-token"
|
|
}
|
|
```
|
|
|
|
## Error Responses
|
|
|
|
| Code | Description |
|
|
|------|-------------|
|
|
| 401 | Invalid or expired refresh token |
|
|
| 400 | Missing refresh token |
|