Summary report

GET /conversations/{conversation_id}/summary_report

Generates a PDF summary of the current conversation — the document to attach to a referral, hand to a clinician, or offer the patient as a download.

Response: 200 OK with media type application/pdf. The body is the PDF bytes, and the response sets:

Content-Disposition: attachment; filename="summary.pdf"

curl "https://api.infermedica.com/api/ct/v2/conversations/68d9a84d-711c-4a55-a9dd-da6363e58e38/summary_report" \
  -H "Authorization: Bearer <token>" \
  -o summary.pdf

The endpoint is a representation read of the current conversation summary; the server may render or cache the document on demand, so treat the first call for a conversation as potentially slower than a cached one.

Because the response is binary rather than JSON, errors are the one case where this endpoint returns the usual JSON error envelope — branch on the content type, not on the presence of a body.