Share one message as a PDF

Request: chat_key + message_key path params (message_key comes from GET /nandini/chats/{chat_key}); Bearer token required; no body

Renders ONE message - either yours or Nandini's - as a branded PDF (the same visual style as report PDFs) and returns its URL, so the app can hand it to the OS share sheet or a download. Nandini's markdown (headers, tables, bullet lists) is flattened into the report-style layout - headers become section headings, table rows become readable lines, bold/italic markers are stripped since the PDF renderer doesn't support inline rich text.

Idempotent: the first call generates and uploads the PDF; every call after that for the SAME message returns the same cached URL instantly (data.cached: true) instead of regenerating - editing a message (see PATCH .../messages/{message_key}) targets a different message_key's worth of content on the regenerated reply, so this never goes stale under an edit.

Success: 200 - data.pdf_url + data.cached

Errors: 401 - invalid/expired token | 404 - chat_key or message_key not found for this user

Bearer Token

Provide your bearer token in the

Authorization

header when making requests to protected resources.

Example:

Authorization: Bearer ********************

Responses

🟢200OK

application/json

Successful Response

Bodyapplication/json

Example

{
    "success": true,
    "message": "Message exported",
    "data": {
        "pdf_url": "https://media.hastaai.in/nandini/exports/6edc7dae-2e76-4dc9-bd11-e6c70d85e581.pdf",
        "cached": false
    }
}

🟠401Unauthorized

🟠404Record Not Found

🟠422Parameter Error

Share one message as a PDF

Request

Request Code Samples

Responses