Mark a thread updated (advanced)

​

Mark a thread's subscriptions as updated now. Optional - use it for server-side integrations and end-to-end tests.

  • Secret key marks every live subscription of the thread; user_id narrows it to one subscriber.
  • Publishable key is limited to the caller's own subscription.

The app_id always comes from the API key, so a key can only touch its own app's threads.

This endpoint appends and marks without any check. On a thread with no new content, generate: true produces a "no new updates" card. The automatic monitor judges content first and never does this, so prefer subscriptions for the real reader experience.

Body·
required
application/json
  • thread_id
    Type: string Format: uuid
    required
  • generate
    Type: boolean

    Also append a generated follow-up answer.

  • user_id
    Type: string

    Secret key only - narrows the change to one subscriber.

Responses
  • application/json
  • application/json
  • 500

    Miso could not read or write the history store. Retry, and keep what you have on screen — this is no longer reported as an empty list.

Request Example for post/v1/ask/user_history/thread/updates/touch
curl 'https://api.askmiso.com/v1/ask/user_history/thread/updates/touch?api_key=YOUR_SECRET_TOKEN' \
  --request POST \
  --header 'Content-Type: application/json' \
  --data '{
  "thread_id": "0e1f2a3b-4c5d-6e7f-8a9b-0c1d2e3f4a5b"
}'

{
  "message": "success",
  "data": {
    "generated": true,
    "question_id": "7c8d9e0f-1a2b-3c4d-5e6f-7a8b9c0d1e2f",
    "touched": 1
  }
}

Success.