Skip to main content
curl "https://api.chroniclehq.com/api/v1/presentations/generate/gen_123/message" \
  -X POST \
  -H "Authorization: Bearer $API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "content": "We help teams turn ideas into polished interactive presentations."
  }'

{
  "status": "generating"
}

Documentation Index

Fetch the complete documentation index at: https://chronicle.mintlify.app/llms.txt

Use this file to discover all available pages before exploring further.

curl "https://api.chroniclehq.com/api/v1/presentations/generate/gen_123/message" \
  -X POST \
  -H "Authorization: Bearer $API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "content": "We help teams turn ideas into polished interactive presentations."
  }'

​
Parameters

​
generationId
string
required
The generation job ID
​
content
string
required
The user’s reply to Chronicle’s clarifying question. Sent as-is into the same generation conversation.

​
Response

After accepting the follow-up, resume polling GET /presentations/generate/:generationId/status on the same generationId. 
{
  "status": "generating"
}
​
status
string
Confirms the follow-up was accepted and generation is resuming. Continue polling the status endpoint with the original generationId.

​
FAQs

Call this endpoint when the generation status is awaiting_input.It sends the user’s response back into the same generation flow.
Yes. Some generation flows require multiple follow-up messages before completion.Continue until the status changes to completed or failed.
Resume polling the generation status endpoint.That tells you whether generation is continuing, needs more input, or has finished.