Explicitly set Telegram chat read/unread state

Requires an explicitly granted write-scoped key and Idempotency-Key. The selected account and chat are resolved together; ambiguous outcomes are not retried. Ordinary history reads remain non-mutating.

post/chats/{chat_id}/read-state

Request

  • Base URL: https://gramclaw.com/api/v1
  • URL: https://gramclaw.com/api/v1/chats/{chat_id}/read-state
  • Auth: HTTP bearer

Path parameters

chat_idstring required

Headers

Idempotency-Keystring required

Stable caller-generated identity for this exact mutation. Ambiguous operations are not retried.

Request body

account_idstring required

Exact workspace-owned GramClaw compatibility account ID.

unreadboolean required

true marks the chat unread; false explicitly marks it read.

Response

The explicit read-state operation was accepted or the exact completed operation was replayed.

Changes

No recorded changes to this operation across all 1 revision of this API.