🐛 Describe the Bug
When calling the Get message by message id API, the response does not contain the attachments field for the call recordings (in case the messageType is TYPE_CALL). Even when calling the Get messages by conversation id, the attachments field is missing for the call recordings.
📍 API Endpoint
https://services.leadconnectorhq.com/conversations/messages/:id
✅ Expected Behavior
The API should return the attachments array as well containing the call recording URL.
💻 Screenshots or Code Samples
{
"message": {
"id": "MfL6JLayiNdO84E2V3bc",
"direction": "outbound",
"status": "completed",
"type": 1,
"locationId": "7lApucujEM8HfQP1IhfS",
"contactId": "9HKMGUXQqklLCDpAj3z9",
"conversationId": "LTWfrzzbn51NpdQxoZJG",
"dateAdded": "2026-02-16T19:52:33.288Z",
"dateUpdated": "2026-02-16T19:53:17.731Z",
"userId": "58PwVuNW0aMEyMuuecZY",
"source": "app",
"meta": {
"call": {
"duration": 37,
"status": "completed"
}
},
"altId": "CA56ee93d85c952ef314f944a6762ba8d4",
"from": "+18135346987",
"to": "+13528577787",
"messageType": "TYPE_CALL"
},
"traceId": "34a59315-fbe7-4b5d-b391-ea8c715c8678"
}Product Area
conversations
📋 Use Case
We need this field to be able to accurately sync the GHL conversation with our CRM.
🚨 Why Should This Be Prioritized?
This should be prioritised because it is blocking our synchronisation of GHL conversations with our CRM.
🧠 Additional Context
No response
🐛 Describe the Bug
When calling the Get message by message id API, the response does not contain the
attachmentsfield for the call recordings (in case the messageType isTYPE_CALL). Even when calling the Get messages by conversation id, theattachmentsfield is missing for the call recordings.📍 API Endpoint
https://services.leadconnectorhq.com/conversations/messages/:id
✅ Expected Behavior
The API should return the
attachmentsarray as well containing the call recording URL.💻 Screenshots or Code Samples
{ "message": { "id": "MfL6JLayiNdO84E2V3bc", "direction": "outbound", "status": "completed", "type": 1, "locationId": "7lApucujEM8HfQP1IhfS", "contactId": "9HKMGUXQqklLCDpAj3z9", "conversationId": "LTWfrzzbn51NpdQxoZJG", "dateAdded": "2026-02-16T19:52:33.288Z", "dateUpdated": "2026-02-16T19:53:17.731Z", "userId": "58PwVuNW0aMEyMuuecZY", "source": "app", "meta": { "call": { "duration": 37, "status": "completed" } }, "altId": "CA56ee93d85c952ef314f944a6762ba8d4", "from": "+18135346987", "to": "+13528577787", "messageType": "TYPE_CALL" }, "traceId": "34a59315-fbe7-4b5d-b391-ea8c715c8678" }Product Area
conversations
📋 Use Case
We need this field to be able to accurately sync the GHL conversation with our CRM.
🚨 Why Should This Be Prioritized?
This should be prioritised because it is blocking our synchronisation of GHL conversations with our CRM.
🧠 Additional Context
No response