API Overview
In addition to the Claude integration, StoryVault offers a REST API for programmatic access. This lets you integrate sessions, transcripts, and projects into your own systems — for example an intranet, a quality management system, or a reporting solution.
The complete API reference with all endpoints, parameters, and examples is accessible after logging in via the API Documentation menu item.
Authentication
Section titled “Authentication”Every API request requires an API key. The key is sent as a Bearer token in the header:
Authorization: Bearer sv_YOUR_KEY_HERECreate API keys under Admin → API Keys.
-
Create an API key
Admin → API Keys → “Create New Key”.
-
Enter a name and optional expiry date
Use a descriptive name, e.g. “Intranet Integration” or “Reporting System”.
-
Copy the key
The key is shown only once. Store it securely.
Available Endpoints
Section titled “Available Endpoints”The API provides access to the main StoryVault resources:
| Area | Endpoints | Description |
|---|---|---|
| Sessions | List, Details, Search | Sessions with status, metadata, and summary |
| Transcripts | Read, Download | Complete transcripts with speaker attribution |
| Projects | List, Details | Projects with associated sessions |
| AI Chat | List chats, read messages | Chat conversations and their history |
| API Keys | Create, List, Revoke | Managing your own API keys |
Rate Limiting
Section titled “Rate Limiting”To ensure stable operation for all users, the following limits apply:
| Limit | Value |
|---|---|
| Requests per minute per key | 60 |
| Behavior when exceeded | HTTP 429 (Too Many Requests) |
When you reach the limit, wait briefly and try again. The Retry-After header in the response indicates how long to wait.
Access Control
Section titled “Access Control”The API key is tied to a user and an organization. Access rights correspond to the user’s role:
- Admins see all data for the organization
- Other roles see only their own sessions and assigned projects
Error Responses
Section titled “Error Responses”The API responds with standard HTTP status codes:
| Code | Meaning |
|---|---|
| 200 | Success |
| 400 | Invalid request (missing or incorrect parameters) |
| 401 | Not authenticated (missing or invalid key) |
| 403 | No permission for this resource |
| 404 | Resource not found |
| 429 | Rate limit reached |
| 500 | Server error |
Practical Examples
Section titled “Practical Examples”Automatic transcript export: An organization automatically exports the transcript to their document management system after each meeting. A script regularly polls for new sessions and downloads the transcripts.
Reporting dashboard: Management integrates StoryVault data into an existing report: number of sessions per month, most common topics, AI usage statistics.
QM software integration: Quality circle minutes are automatically transferred to the QM system. Summaries and action items are immediately available in the existing documentation.
API Documentation
Section titled “API Documentation”The full developer documentation with endpoints, parameters, request/response formats, and code examples is accessible after logging in via the API Documentation menu item.
Further Reading
Section titled “Further Reading”This page describes the REST API for programmatic access to StoryVault.