API Reference
Read one conversation
Try it — GET /conversations/{id}
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:readAuthorizationBearer <token>
Authorization: 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:read
Path Parameters
id*string
The prefixed id of the object.
Response Body
application/json
application/json
application/json
application/json
application/json
curl -X GET https://app.sendkuy.com/api/v1/conversations/cnv_9cBe3A1H-SLhW5fONWZ32wb-IIio5Ts3 \ -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" }}