API for managing personal memory items with authentication and user-specific data.
API for managing personal memory items with authentication and user-specific data.
This API supports three authentication methods:
X-API-Key headerX-API-Key: <your-api-key>X-Session-Token headerX-Session-Token: <your-session-token>Authorization headerAuthorization: Bearer <token>All endpoints require one of these authentication methods.
Upload and process documents using the pluggable architecture.
Authentication Required: Bearer token or API key
Supported Providers: TensorLake.ai, Reducto AI, Gemini Vision (fallback)
Features:
Preferred provider for document processing.
Preferred provider for document processing.
JSON-encoded memory policy. Includes mode ('auto'/'manual'), schema_id, node_constraints (applied in auto mode when present), and OMO fields (consent, risk, acl). This is the recommended way to configure memory processing.
JSON-encoded memory policy. Includes mode ('auto'/'manual'), schema_id, node_constraints (applied in auto mode when present), and OMO fields (consent, risk, acl). This is the recommended way to configure memory processing.
JSON-encoded memory policy. Includes mode ('auto'/'manual'), schema_id, node_constraints (applied in auto mode when present), and OMO fields (consent, risk, acl). This is the recommended way to configure memory processing.
Your application's user identifier. This is the primary way to identify users. Also accepts legacy 'end_user_id'.
Your application's user identifier. This is the primary way to identify users. Also accepts legacy 'end_user_id'.
Your application's user identifier. This is the primary way to identify users. Also accepts legacy 'end_user_id'.
DEPRECATED: Internal Papr Parse user ID. Most developers should use external_user_id.
DEPRECATED: Internal Papr Parse user ID. Most developers should use external_user_id.
DEPRECATED: Internal Papr Parse user ID. Most developers should use external_user_id.
curl -i -X POST \
http://memory.papr.ai/v1/document \
-H 'Authorization: Bearer <YOUR_JWT_HERE>' \
-H 'Content-Type: multipart/form-data' \
-F file=string \
-F preferred_provider=gemini \
-F hierarchical_enabled=true \
-F schema_id=string \
-F graph_override=string \
-F property_overrides=string \
-F memory_policy=string \
-F namespace_id=string \
-F external_user_id=string \
-F user_id=string \
-F webhook_url=string \
-F webhook_secret=string \
-F metadata=stringDocument upload started
Human-readable status message
Human-readable status message
Human-readable status message
Error message if failed
Error message if failed
Error message if failed
Additional error details or context
Additional error details or context
Additional error details or context
Status and progress of the document upload
Post ID in Parse Server (user-facing page ID)
Post ID in Parse Server (user-facing page ID)
Post ID in Parse Server (user-facing page ID)
Processing status type
Processing status type
Processing status type
{ "code": 200, "status": "success", "message": "string", "error": "string", "details": {}, "document_status": { "progress": 0, "current_page": 0, "total_pages": 0, "current_filename": "string", "upload_id": "string", "page_id": "string", "status_type": "processing", "error": "string" }, "memory_items": [ { … } ], "memories": [ { … } ] }
curl -i -X GET \
'http://memory.papr.ai/v1/document/status/{upload_id}' \
-H 'Authorization: Bearer <YOUR_JWT_HERE>'{}
curl -i -X DELETE \
'http://memory.papr.ai/v1/document/{upload_id}' \
-H 'Authorization: Bearer <YOUR_JWT_HERE>'{}