Get Conversation History

GET /api/chat/history

Get Conversation History

cURL

curl --request GET \
  --url https://api.example.com/api/chat/history

import requests

url = "https://api.example.com/api/chat/history"

response = requests.get(url)

print(response.text)

const options = {method: 'GET'};

fetch('https://api.example.com/api/chat/history', options)
  .then(res => res.json())
  .then(res => console.log(res))
  .catch(err => console.error(err));

<?php

$curl = curl_init();

curl_setopt_array($curl, [
  CURLOPT_URL => "https://api.example.com/api/chat/history",
  CURLOPT_RETURNTRANSFER => true,
  CURLOPT_ENCODING => "",
  CURLOPT_MAXREDIRS => 10,
  CURLOPT_TIMEOUT => 30,
  CURLOPT_HTTP_VERSION => CURL_HTTP_VERSION_1_1,
  CURLOPT_CUSTOMREQUEST => "GET",
]);

$response = curl_exec($curl);
$err = curl_error($curl);

curl_close($curl);

if ($err) {
  echo "cURL Error #:" . $err;
} else {
  echo $response;
}

package main

import (
	"fmt"
	"net/http"
	"io"
)

func main() {

	url := "https://api.example.com/api/chat/history"

	req, _ := http.NewRequest("GET", url, nil)

	res, _ := http.DefaultClient.Do(req)

	defer res.Body.Close()
	body, _ := io.ReadAll(res.Body)

	fmt.Println(string(body))

}

HttpResponse<String> response = Unirest.get("https://api.example.com/api/chat/history")
  .asString();

require 'uri'
require 'net/http'

url = URI("https://api.example.com/api/chat/history")

http = Net::HTTP.new(url.host, url.port)
http.use_ssl = true

request = Net::HTTP::Get.new(url)

response = http.request(request)
puts response.read_body

200

{
  "history": [
    {
      "role": {},
      "content": "<string>",
      "timestamp": "<string>",
      "original_recipe": {},
      "suggested_recipe": {},
      "accepted": true
    }
  ]
}

This endpoint is currently not implemented in the backend. The chat system uses LangGraph’s built-in memory management with thread-based context.

Planned Implementation

Conversation history is maintained automatically by the AI assistant using thread IDs formatted as {user_id}-{date}. Each day creates a new conversation thread, and context is preserved within the same day’s interactions.

Alternative: Thread-Based Context

The SmartEat AI chat system currently uses LangGraph’s state management to maintain conversation context:

• Thread ID Format: {user_id}-{current_date}
• Context Window: Conversations are scoped to the current day
• State Persistence: Message history is maintained in-memory during the session
• Profile & Plan Access: The assistant always has access to your current profile and active meal plan

Example Current Behavior

When you send multiple messages in a day, the assistant maintains context:

First Message

curl -X POST https://api.smarteat.ai/api/chat/ \
  -H "Authorization: Bearer <token>" \
  -d 'message=Create a meal plan for me'

# Response: "I've created a 7-day meal plan..."

Follow-up Message (Same Day)

curl -X POST https://api.smarteat.ai/api/chat/ \
  -H "Authorization: Bearer <token>" \
  -d 'message=Can you swap the dinner for day 1?'

# Response: "I'll swap the dinner recipe from your meal plan..." 
# (Assistant remembers the plan it just created)

Schema Definition

When this endpoint is implemented, it will return conversation history using the following schema:

Response Structure

history · array

Array of messages in chronological order

Show Message object

role · enum

Role of the message sender

• user - Message from the user
• chef - Message from the AI assistant

content · string

The message content

timestamp · string

ISO 8601 timestamp of when the message was sent

original_recipe · object

Only present for suggestion messages - the original recipe being replaced

suggested_recipe · object

Only present for suggestion messages - the new recipe being suggested

accepted · boolean

Only present for suggestion messages - whether the user accepted the suggestion

Future Implementation Example

200 - Success (Planned)

{
  "history": [
    {
      "role": "user",
      "content": "Create a meal plan for this week",
      "timestamp": "2026-03-05T10:30:00Z"
    },
    {
      "role": "chef",
      "content": "I've created a 7-day meal plan for you with 3 meals per day...",
      "timestamp": "2026-03-05T10:30:05Z"
    },
    {
      "role": "user",
      "content": "Can you swap the dinner for day 1?",
      "timestamp": "2026-03-05T10:32:00Z"
    },
    {
      "role": "chef",
      "content": "I've found a similar recipe that matches your preferences...",
      "timestamp": "2026-03-05T10:32:03Z",
      "original_recipe": {
        "id": 1,
        "name": "Grilled Chicken Salad",
        "calories": 450
      },
      "suggested_recipe": {
        "id": 2,
        "name": "Mediterranean Chicken Bowl",
        "calories": 480
      },
      "accepted": true
    }
  ]
}

Notes

• Conversation history may be implemented in a future version
• Current implementation relies on LangGraph’s state management
• Each day starts a new conversation thread
• Consider implementing persistent storage for long-term conversation history