chat.mark_readMark messages through the selected message as read by the user. Call only after the user has reviewed them; fetching messages alone is not a read receipt.
- Operation
- write
- OAuth scopes
- mcp
Availability depends on your assigned tools. Scopes do not grant record access. Read the tool description and current resource before changing it; follow the required revision and idempotency fields below.
Client portal inputs
| Name and description | Required |
|---|---|
conversation_idConversation slug returned in the id field by chat.list. Copy it exactly; do not use the group name or a database ID. | Yes |
idempotency_keySee the input schema for constraints. | Yes |
message_idSee the input schema for constraints. | Yes |
organization_slugSee the input schema for constraints. | Yes |
provider_slugSee the input schema for constraints. | Yes |
View exact input schema
Provider portal inputs
| Name and description | Required |
|---|---|
conversation_idConversation slug returned in the id field by chat.list. Copy it exactly; do not use the group name or a database ID. | Yes |
idempotency_keySee the input schema for constraints. | Yes |
message_idSee the input schema for constraints. | Yes |
provider_slugCopy the provider slug from providers.list or your client workspace. | Yes |
View exact input schema
Result
Check the structured result for success or an error before continuing. Read the affected record to confirm your change.
View exact output schema
For this workflow’s steps and prerequisites, read the Chat and messages guide.
