API Reference
The Hypersave API is organized around REST. Our API has predictable resource-oriented URLs, accepts JSON-encoded request bodies, returns JSON-encoded responses, and uses standard HTTP response codes.
Base URL
All API requests should be made to:
https://api.hypersave.ioEndpoints Overview
| Method | Endpoint | Description |
|---|---|---|
POST | /v1/save | Save content to memory |
POST | /v1/ask | Ask questions about your memories |
POST | /v1/search | Semantic search across memories |
POST | /v1/query | Query memories with filters |
GET | /v1/memories | List all memories |
DELETE | /v1/memory/:id | Delete a specific memory |
POST | /v1/remind | Get contextual reminders |
GET | /v1/graph | Get knowledge graph |
GET | /v1/facts | Get extracted facts |
GET | /v1/entities | Get extracted entities |
POST | /v1/ingest | Bulk ingest content |
POST | /v1/turbo/save | Turbo mode save |
POST | /v1/turbo/ask | Turbo mode ask |
GET | /v1/profile | Get user profile |
GET | /v1/usage | Get usage statistics |
Request Format
All requests must include the following headers:
Authorization: Bearer YOUR_API_KEY
Content-Type: application/jsonResponse Format
All responses follow a consistent format:
{
"success": true,
"data": { ... },
"message": "Operation completed successfully"
}Error Response
{
"success": false,
"error": "Error code",
"message": "Human-readable error message",
"details": { ... }
}HTTP Status Codes
| Code | Description |
|---|---|
200 | Success |
201 | Created |
400 | Bad Request - Invalid parameters |
401 | Unauthorized - Invalid or missing API key |
403 | Forbidden - Insufficient permissions |
404 | Not Found - Resource doesn't exist |
429 | Too Many Requests - Rate limit exceeded |
500 | Internal Server Error |
Rate Limits
Rate limits vary by plan:
| Plan | Requests/Hour | Requests/Month |
|---|---|---|
| Free | 100 | 10,000 |
| Pro | 1,000 | 100,000 |
| Enterprise | Unlimited | Unlimited |
When you exceed your rate limit, you'll receive a 429 response with a Retry-After header.
Pagination
List endpoints support pagination using limit and offset parameters:
GET /v1/memories?limit=20&offset=40Response includes pagination metadata:
{
"success": true,
"data": [...],
"pagination": {
"limit": 20,
"offset": 40,
"total": 150,
"hasMore": true
}
}