Mark a conversation as read
Sets unread_count to zero. Answers with the conversation.
Try it — POST /conversations/{id}/read
Kept for this tab only — it disappears when you close it, and it is never sent anywhere except as the Authorization header on the call below.
Authorization
bearerAuth inbox:writeAuthorization: Bearer sk_live_.... Keys in the query string or the
request body are refused — a URL is logged by every proxy it passes,
and that is how customer keys leak.
A key carries scopes. A call outside them answers 403 with
insufficient_scope and names the scope it wanted.
In: header
Scope: inbox:write
Path Parameters
The prefixed id of the object.
Header Parameters
Any unique string, one per logical request. Retrying with the same key
returns the first answer instead of doing the work twice, and answers
with Idempotent-Replay: true.
length <= 255Response Body
application/json
application/json
application/json
application/json
application/json
application/json
curl -X POST https://app.sendkuy.com/api/v1/conversations/cnv_9cBe3A1H-SLhW5fONWZ32wb-IIio5Ts3/read \ -H "Authorization: Bearer sk_live_YOUR_API_KEY"{ "data": { "object": "conversation", "id": "cnv_9cBe3A1H-SLhW5fONWZ32wb-IIio5Ts3", "channel": "string", "status": "string", "contact_id": "string", "unread_count": 0, "last_message_at": "2019-08-24T14:15:22Z", "created_at": "2019-08-24T14:15:22Z", "updated_at": "2019-08-24T14:15:22Z" }}Read the messages in a conversation GET
These are conversation_message objects with cms_ ids, not the msg_ delivery rows you get from GET /messages. Different things, different prefixes.
Reply in a conversation POST
Answers 201 with the **conversation_message** that was created — not the conversation, and not a msg_ delivery row.