v1
Messages
Store Message
Changed onStore a chat message and queue it for AI analysis and memory creation.
**Authentication Required**: Bearer token, API key, or session token
**Processing Control**:
- Set `process_messages: true` (default) to enable full AI analysis and memory creation
- Set `process_messages: false` to store messages only without processing into memories
**Processing Flow** (when process_messages=true):
1. Message is immediately stored in PostMessage class
2. Background processing analyzes the message for memory-worthiness
3. If worthy, creates a memory with appropriate role-based categorization
4. Links the message to the created memory
**Role-Based Categories**:
- **User messages**: preference, task, goal, facts, context
- **Assistant messages**: skills, learning
**Session Management**:
- `sessionId` is required to group related messages
- Use the same `sessionId` for an entire conversation
- **Optional `title`**: Set a human-readable title for the conversation (e.g., "Q4 Planning Session")
- Retrieve conversation history using GET /messages/sessions/{sessionId}
post/v1/messages
Request
- Base URLhttps://memory.papr.ai
- URLhttps://memory.papr.ai/v1/messages
- Auth
- API key in header X-API-Key
- or HTTP bearer
Request body
Example request
{
"content": "Can you help me plan the Q4 product roadmap?",
"metadata": {
"location": "Office",
"topics": [
"product",
"planning",
"roadmap"
]
},
"process_messages": true,
"role": "user",
"sessionId": "session_123",
"title": "Q4 Product Planning"
}Response
Message stored and queued for processing
Example response
{
"content": "Can you help me plan the Q4 product roadmap?",
"createdAt": "2024-01-15T10:30:00Z",
"objectId": "msg_abc123",
"processing_status": "queued",
"role": "user",
"sessionId": "session_123"
}Changes
- breaking
removed from the
request propertyanyOflist - breaking
removed from the
//request propertyanyOflist - info
added the new optional request property
- info
added the new optional request property
- info
added
subschema #1to the//request propertyanyOflist - info
added
subschema #2to therequest propertyanyOflist - info
added
subschema #2to theresponse propertyanyOflist for the response status - info
removed from the
response propertyanyOflist for the response status
- breaking
- breaking
removed
subschema #1from the//request propertyanyOflist - warning
removed the request property
- warning
removed the request property
- info
added to the
//request propertyanyOflist
- breaking