open-notebook/docs/7-DEVELOPMENT/api-reference.md
Luis Novo 3f352cfcce
feat: credential-based API key management (#477) (#540)
* feat: replace provider config with credential-based system (#477)

Introduce a new credential management system replacing the old
ProviderConfig singleton and standalone Models page. Each credential
stores encrypted API keys and provider-specific configuration with
full CRUD support via a unified settings UI.

Backend:
- Add Credential domain model with encrypted API key storage
- Add credentials API router (CRUD, discovery, registration, testing)
- Add encryption utilities for secure key storage
- Add key_provider for DB-first env-var fallback provisioning
- Add connection tester and model discovery services
- Integrate ModelManager with credential-based config
- Add provider name normalization for Esperanto compatibility
- Add database migrations 11-12 for credential schema

Frontend:
- Rewrite settings/api-keys page with credential management UI
- Add model discovery dialog with search and custom model support
- Add compact default model assignments (primary/advanced layout)
- Add inline model testing and credential connection testing
- Add env-var migration banner
- Update navigation to unified settings page
- Remove standalone models page and old settings components

i18n:
- Update all 7 locale files with credential and model management keys

Closes #477

Co-Authored-By: JFMD <git@jfmd.us>
Co-Authored-By: OraCatQAQ <570768706@qq.com>

* fix: address PR #540 review comments

- Fix docs referencing removed Models page
- Fix error-handler returning raw messages instead of i18n keys
- Fix auth.py misleading docstring and missing no-password guard
- Fix connection_tester using wrong env var for openai_compatible
- Add provision_provider_keys before model discovery/sync
- Update CLAUDE.md to reflect credential-based system
- Fix missing closing brace in api-keys page useEffect

* fix: add logging to credential migration and surface errors in UI

- Add comprehensive logging to migrate-from-env and
  migrate-from-provider-config endpoints (start, per-provider
  progress, success/failure with stack traces, final summary)
- Fix frontend migration hooks ignoring errors array from response
- Show error toast when migration fails instead of "nothing to migrate"
- Invalidate status/envStatus queries after migration so banner updates

* docs: update CLAUDE.md files for credential system

Replace stale ProviderConfig and /api-keys/ references across 8 CLAUDE.md
files to reflect the new Credential-based system from PR #540.

* docs: update user documentation for credential-based system

Replace env var API key instructions with Settings UI credential
workflow across all user-facing documentation. The new flow is:
set OPEN_NOTEBOOK_ENCRYPTION_KEY → start services → add credential
in Settings UI → test → discover models → register.

- Rewrite ai-providers.md, api-configuration.md, environment-reference.md
- Update all quick-start guides and installation docs
- Update ollama.md, openai-compatible.md, local-tts/stt networking sections
- Update reverse-proxy.md, development-setup.md, security.md
- Fix broken links to non-existent docs/deployment/ paths
- Add credentials endpoints to api-reference.md
- Move all API key env vars to deprecated/legacy sections

* chore: bump version to 1.7.0-rc1

Release candidate for credential-based provider management system.

* fix: initialize provider before try block in test_credential

Prevents UnboundLocalError when Credential.get() throws (e.g.,
invalid credential_id) before provider is assigned.

* fix: reorder down migration to drop index before table

Removes duplicate REMOVE FIELD statement and reorders so the index
is dropped before the table, preventing rollback failures.

* refactor: simplify encryption key to always derive via SHA-256

Remove the dual code path in _ensure_fernet_key() that detected native
Fernet keys. Since the credential system is new, always deriving via
SHA-256 removes unnecessary complexity. Also removes the generate_key()
function and Fernet.generate_key() references from docs.

* fix: correct mock patch targets in embedding tests and URL validation

Fix embedding tests patching wrong module path for model_manager
(was targeting open_notebook.utils.embedding.model_manager but it's
imported locally from open_notebook.ai.models). Also fix URL validation
to allow unresolvable hostnames since they may be valid in the
deployment environment (e.g., Azure endpoints, internal DNS).

* feat: add global setup banner for encryption and migration status

Show a persistent banner in AppShell when encryption key is missing
(red) or env var API keys can be migrated (amber), so users see
these prompts on every page instead of only on Settings > API Keys.

Includes a docs link for the encryption banner and i18n support
across all 7 locales.

* docs: several improvements to docker-compose e env examples

* Update README.md

Co-authored-by: cubic-dev-ai[bot] <191113872+cubic-dev-ai[bot]@users.noreply.github.com>

* docs: fix env var format in README and update model setup instructions

Align the encryption key snippet in README Step 2 with the list
format used in the compose file. Replace deprecated "Settings →
Models" instructions with credential-based Discover Models flow.

* fix: address credential system review issues

- Fix SSRF bypass via IPv4-mapped IPv6 addresses (::ffff:169.254.x.x)
- Fix TTS connection test missing config parameter
- Add Azure-specific model discovery using api-key auth header
- Add Vertex static model list for credential-based discovery
- Fix PROVIDER_DISCOVERY_FUNCTIONS incorrect azure/vertex mapping
- Extract business logic to api/credentials_service.py (service layer)
- Move credential Pydantic schemas to api/models.py
- Update tests to use new service imports and ValueError assertions

* fix: sanitize error responses and migrate key_provider to Credential

- Replace raw exception messages in all credential router 500 responses
  with generic error strings (internal details logged server-side only)
- Refactor key_provider.py to use Credential.get_by_provider() instead
  of deprecated ProviderConfig.get_instance()
- Remove unused functions (get_provider_configs, get_default_api_key,
  get_provider_config) that were dead code

---------

Co-authored-by: JFMD <git@jfmd.us>
Co-authored-by: OraCatQAQ <570768706@qq.com>
2026-02-10 08:30:22 -03:00

6.7 KiB

API Reference

Complete REST API for Open Notebook. All endpoints are served from the API backend (default: http://localhost:5055).

Base URL: http://localhost:5055 (development) or environment-specific production URL

Interactive Docs: Use FastAPI's built-in Swagger UI at http://localhost:5055/docs for live testing and exploration. This is the primary reference for all endpoints, request/response schemas, and real-time testing.


Quick Start

1. Authentication

Simple password-based (development only):

curl http://localhost:5055/api/notebooks \
  -H "Authorization: Bearer your_password"

⚠️ Production: Replace with OAuth/JWT. See Security Configuration for details.

2. Base API Flow

Most operations follow this pattern:

  1. Create a Notebook (container for research)
  2. Add Sources (PDFs, URLs, text)
  3. Query via Chat or Search
  4. View results and Notes

3. Testing Endpoints

Instead of memorizing endpoints, use the interactive API docs:

  • Navigate to http://localhost:5055/docs
  • Try requests directly in the browser
  • See request/response schemas in real-time
  • Test with your own data

API Endpoints Overview

Main Resource Types

Notebooks - Research projects containing sources and notes

  • GET/POST /notebooks - List and create
  • GET/PUT/DELETE /notebooks/{id} - Read, update, delete

Sources - Content items (PDFs, URLs, text)

  • GET/POST /sources - List and add content
  • GET /sources/{id} - Fetch source details
  • POST /sources/{id}/retry - Retry failed processing
  • GET /sources/{id}/download - Download original file

Notes - User-created or AI-generated research notes

  • GET/POST /notes - List and create
  • GET/PUT/DELETE /notes/{id} - Read, update, delete

Chat - Conversational AI interface

  • GET/POST /chat/sessions - Manage chat sessions
  • POST /chat/execute - Send message and get response
  • POST /chat/context/build - Prepare context for chat

Search - Find content by text or semantic similarity

  • POST /search - Full-text or vector search
  • POST /ask - Ask a question (search + synthesize)

Transformations - Custom prompts for extracting insights

  • GET/POST /transformations - Create custom extraction rules
  • POST /sources/{id}/insights - Apply transformation to source

Models - Configure AI providers

  • GET /models - Available models
  • GET /models/defaults - Current defaults
  • POST /models/config - Set defaults

Credentials - Manage AI provider credentials

  • GET/POST /credentials - List and create credentials
  • GET/PUT/DELETE /credentials/{id} - CRUD operations
  • POST /credentials/{id}/test - Test connection
  • POST /credentials/{id}/discover - Discover models from provider
  • POST /credentials/{id}/register-models - Register discovered models
  • GET /credentials/status - Provider status overview
  • GET /credentials/env-status - Environment variable status
  • POST /credentials/migrate-from-env - Migrate env vars to credentials

Health & Status

  • GET /health - Health check
  • GET /commands/{id} - Track async operations

Authentication

Current (Development)

All requests require password header:

curl -H "Authorization: Bearer your_password" http://localhost:5055/api/notebooks

Password configured via OPEN_NOTEBOOK_PASSWORD environment variable.

📖 See Security Configuration for complete authentication setup, API examples, and production hardening.

Production

⚠️ Not secure. Replace with:

  • OAuth 2.0 (recommended)
  • JWT tokens
  • API keys

See Security Configuration for production setup.


Common Patterns

Pagination

# List sources with limit/offset
curl 'http://localhost:5055/sources?limit=20&offset=10'

Filtering & Sorting

# Filter by notebook, sort by date
curl 'http://localhost:5055/sources?notebook_id=notebook:abc&sort_by=created&sort_order=asc'

Async Operations

Some operations (source processing, podcast generation) return immediately with a command ID:

# Submit async operation
curl -X POST http://localhost:5055/sources -F async_processing=true
# Response: {"id": "source:src001", "command_id": "command:cmd123"}

# Poll status
curl http://localhost:5055/commands/command:cmd123

Streaming Responses

The /ask endpoint streams responses as Server-Sent Events:

curl -N 'http://localhost:5055/ask' \
  -H "Content-Type: application/json" \
  -d '{"question": "What is AI?"}'

# Outputs: data: {"type":"strategy",...}
#          data: {"type":"answer",...}
#          data: {"type":"final_answer",...}

Multipart File Upload

curl -X POST http://localhost:5055/sources \
  -F "type=upload" \
  -F "notebook_id=notebook:abc" \
  -F "file=@document.pdf"

Error Handling

All errors return JSON with status code:

{"detail": "Notebook not found"}

Common Status Codes

Code Meaning Example
200 Success Operation completed
400 Bad Request Invalid input
404 Not Found Resource doesn't exist
409 Conflict Resource already exists
500 Server Error Database/processing error

Tips for Developers

  1. Start with interactive docs (http://localhost:5055/docs) - this is the definitive reference
  2. Enable logging for debugging (check API logs: docker logs)
  3. Streaming endpoints require special handling (Server-Sent Events, not standard JSON)
  4. Async operations return immediately; always poll status before assuming completion
  5. Vector search requires embedding model configured (check /models)
  6. Model overrides are per-request; set in body, not config
  7. CORS enabled in development; configure for production

Learning Path

  1. Authentication: Add X-Password header to all requests
  2. Create a notebook: POST /notebooks with name and description
  3. Add a source: POST /sources with file, URL, or text
  4. Query your content: POST /chat/execute to ask questions
  5. Explore advanced features: Search, transformations, streaming

Production Considerations

  • Replace password auth with OAuth/JWT (see Security)
  • Add rate limiting via reverse proxy (Nginx, CloudFlare, Kong)
  • Enable CORS restrictions (currently allows all origins)
  • Use HTTPS via reverse proxy (see Reverse Proxy)
  • Set up API versioning strategy (currently implicit)

See Security Configuration and Reverse Proxy Setup for complete production setup.