sayintel
Endpoint

Update message

POST/api/public/v1/messages/{message_id}write

Edit drafted message content. Cannot edit a message after it is sent. The old QA verdict is cleared (it described text that no longer exists, including any hard-fail codes in qa_flags) and the row is stamped founder_edited, which protects your wording from every automated rewrite path. It is not send-ready until scored: nothing re-scores an edited row on its own, so run rescore_drafts on the speaker to score the new text. A clean score releases it; founder_edited alone never holds a row.

Request

curl -X POST "https://sayintel.com/api/public/v1/messages/<message_id>" \
  -H "Authorization: Bearer $SAYINTEL_TOKEN" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{"content": "<content>"}'

Try it out

Try it outPOST/api/public/v1/messages/{message_id}write

Sent as a bearer token to this site only, and kept in this tab's session storage. It is never written to disk or sent anywhere else.

Paste an API key to run.

Path parameters

NameInTypeRequiredDescription
message_idpathstringyes—

Body

NameInTypeRequiredDescription
contentbodystringyes—

Response

{
  "ok": true,
  "tool": "update_message",
  "kind": "write",
  "data": { ... },
  "error": null
}

Notes

  • Scope required: write. How scopes work.
  • Accepts Idempotency-Key. A retry with the same key replays the first result instead of repeating the work.
  • Same capability over MCP as the tool update_message. MCP setup.