Files
bookhoard/docs/developer/api/authentication/refresh_token.md
T
john-okeefe 253f56399d docs: restructure documentation into audience-based portals
BREAKING CHANGE: Documentation URLs have changed

New structure:
- user/ - End-user documentation (device setup, sync guides, frontend)
- developer/ - Developer documentation (API reference, protocols, specs)
- operations/ - Operations documentation (deployment, troubleshooting)
- contributing/ - Contribution guides

Changes:
- Created portal INDEX.md files for each audience section
- Moved device guides to user/devices/ (kobo-setup.md, koreader-setup.md)
- Moved API docs to developer/ (api-reference.md, collections-api.md)
- Moved sync guide to user/sync-guide.md
- Moved troubleshooting to operations/troubleshooting.md
- Moved all split API docs to developer/api/
- Renamed protocol files (kobo-protocol.md, koreader-protocol.md)
- Added placeholder user guides (frontend, user-areas, settings, admin)
- Updated all internal links to new paths
- Updated Go code (http_handler.go, navigation.go) for new paths
- Updated main INDEX.md for audience-based navigation

Benefits:
- Clear separation of user and developer documentation
- Scalable structure for future user guide expansion
- Better organization and discoverability
- Audience-specific landing pages

Related to DOCS_IMPLEMENTATION_PLAN.md Phase 2 completion
2026-02-02 15:58:34 -05:00

733 B

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

{
  "refresh_token": "d4f5g6h7..."
}

Response (200 OK)

{
  "token": "new-jwt-token",
  "refresh_token": "new-refresh-token"
}

Error Responses

Code Description
401 Invalid or expired refresh token
400 Missing refresh token

Try It Out