POST /presentations/generate/:generationId/message

Sends a follow-up message within an active generation job.

cURL

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."
  }'

Response

{
  "status": "generating"
}

cURL

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.

Response

{
  "status": "generating"
}

status · string

Confirms the follow-up was accepted and generation is resuming. Continue polling the status endpoint with the original generationId.

---

FAQs

When should I call this endpoint?

Call this endpoint when the generation status is awaiting_input.

It sends the user’s response back into the same generation flow.

Can generation require more than one follow-up message?

Yes. Some generation flows require multiple follow-up messages before completion.

Continue until the status changes to completed or failed.

What should I do after sending a follow-up message?

Resume polling the generation status endpoint.

That tells you whether generation is continuing, needs more input, or has finished.

---

Related posts

• GET /presentations/generate/:generationId/status
• POST /presentations/generate
• API scope and rate limits