Skip to main content
GET
/
api
/
conversation
/
{conversationId}
Chat with knowledge base
curl --request GET \
  --url https://api.getpoppy.ai/api/conversation/{conversationId} \
  --header 'x-api-key: <api-key>'
{
  "text": "I apologize for the confusion. According to the information you provided earlier, your favorite number is 444.",
  "credits_used": 0.02885,
  "credits_remaining": 1853.71700
}
This endpoint lets you continue an ongoing conversation with your assistant, keeping the context from previous messages.

URL Parameters

conversationId
string
required
The ID of the to continue the conversation with

Query Parameters

api_key
string
Your API key for authentication
board_id
string
required
The ID of the board to use for the conversation
chat_id
string
required
The ID of the chat node within the board
prompt
string
required
The follow-up question or prompt for the AI
model
string
default:"claude-4-sonnet-20250514"
The AI model to use. Allowed values: claude-4-sonnet-20250514, o3-mini, gpt-4o, grok-2-1212, gpt-4o-mini
save_history
boolean
Whether save the answer in the chat
plaintext
string
default:false
Force the AI response to use plain text instead of markdown. Allowed values are “true” or “active”. Any other value will disable plaintext.
streaming
string
default:false
Return the answer as a stream instead of a JSON. Allowed values are “true” or “active”. Any other value will disable streaming.
additional_context
string
default:" "
Additional information to provide as context to the AI
user
string
Optional user identifier
source
string
Optional source of the request

Response

text
string
The AI-generated response to the prompt
credits_used
number
The number of credits used for this request
credits_remaining
number
The total number of credits remaining in your account
{
  "text": "I apologize for the confusion. According to the information you provided earlier, your favorite number is 444.",
  "credits_used": 0.02885,
  "credits_remaining": 1853.71700
}
This endpoint is functionally equivalent to the POST /api/conversation/ endpoint, but allows for easier testing and integration in contexts where POST requests are difficult to implement.
I