Quick reply

Follow-ups use the same endpoint as new prompts: POST /users/run-models. Include questionHistory with your new question. The API may issue an extra /quick-reply request and merge a quickReply field into the main JSON response when present.

Typical companion fields

The auxiliary request generally carries your current question, user identifiers (id, organisationId, modelType, optional modelId, optional buildingIds), inactiveOrgMemoryIds, and questionHistory.

If quick reply is unavailable

Failures in the auxiliary step do not fail the whole call—you still receive the main model response. If quick replies never appear, verify your payload and contact support with request ids if needed.

Example JSON

{
  "question": "Can you expand on the second bullet?",
  "user": {
    "id": "00000000-0000-0000-0000-000000000000",
    "organisationId": "00000000-0000-0000-0000-000000000000",
    "modelType": "leniq-pro"
  },
  "questionHistory": [
    { "role": "user", "content": "…" },
    { "role": "assistant", "content": "…" }
  ],
  "tone": "professional"
}

Multipart and file rules are the same as on Run models.