Course Assistant Turn
One assistant turn: send the client’s message, get the reply and the next question.
When the course’s uploaded documents have been digested, the response may
carry a suggestion object for the served question:
{question_id, theme, say, candidate, evidence, status}. candidate is the
full pre-validated value a confirm would record (every field shown, exactly
as stored); evidence quotes the client’s own documents. While the digest is
still building (or failed, or the course has no sources) the field is simply
omitted and the turn proceeds normally.
To accept a suggestion, send confirm: {question_id, value?} instead of a
message. The server validates and records it exactly like a typed answer
(source='text') with zero model calls; value overrides the stored
candidate when the client edited the surface. Errors: 400 confirm_not_current
(the id is not the question currently served), 400 confirm_no_candidate
(nothing stored to confirm and no value supplied). Confirm turns are
idempotent under client_turn_id like any other turn.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Body
1 - 1288000Explicit confirmation of the served question's document suggestion. A confirm turn makes zero model calls; the answer is validated and recorded by the server exactly as a typed answer would be (source='text').
Response
Successful Response