Get all messages for a specific thread
const url = 'https://open-api.replyco.com/openapi/message/threadmessages/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0';const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://open-api.replyco.com/openapi/message/threadmessages/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0 \ --header 'Authorization: Bearer <token>'Returns all messages (both customer-facing and internal notes) for a thread. Messages are ordered chronologically (oldest first).
Includes:
- Customer messages
- Internal notes
- System messages
- Attachments metadata
- Sender information
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”Thread ID to retrieve messages from
Responses
Section titled “Responses”Returns the list of thread messages
object
Usually field contains List with MailMessageId of thread messages
Mail Uid
If we sent message then message id from company
Second type of MarketMessageID (needs when market Api use different types of message id for reply or other function)
object
An attachment as it is returned by the API. Unlike the request model it never carries the file content, so responses stay small. To download the original file, get a link from GET /openApi/byteFiles/messageAttachments/{messageId}/links.
object
Path of the stored file. Pass it back as ‘url’ on a later request to re-use the same file without uploading it again.
The name of the file including its extension (e.g., “invoice.pdf”, “image.jpg”)
ID of a small 180x120 cropped thumbnail of this attachment, available from GET /openApi/byteFiles/{id}. It is not the original file. Null when no thumbnail was generated (for example, for files hosted by eBay)
Size of the file in kilobytes
Example
[ { "status": "0 - SentSuccesfully", "language": "0 - None" }]User is not authenticated or authorized
User does not have access to this thread
Thread with the specified ID was not found