Conversations & messages
Read customer conversation history from your own backend.
Follow a customer’s history
GET /customers/{customer}/conversations lists that customer’s conversations. GET /conversations lists workspace conversations, with optional customer_id and status filters. The key needs conversations:read, including when the path contains a customer ID.
A conversation contains its public ID, customer ID, subject, status, priority, channel, origin and creation/update timestamps. Status and priority are workspace values; do not assume every workspace uses the same custom values.
curl "https://trucom.app/api/v1/rest/customers/CUSTOMER_ID/conversations?per_page=25" \
-H "Authorization: Bearer $TRUCOM_API_KEY"Read public messages
GET /conversations/{conversation}/messages returns public messages in creation order, oldest first. Internal notes, system events, deleted messages, credentials and arbitrary internal metadata are excluded.
Messages include sender type and display name, body, attachment count and available delivery timestamps. Attachment counts describe files attached to a message; this endpoint does not include download URLs. Treat bodies as untrusted text when rendering them.
Conversation endpoints in this API provide read access. Use the widget for the customer messaging experience. A server API key has workspace-wide access according to its scopes; your application must authorize its own users before showing them any API data.