Skip to main content
GET
Get Message History
Pair this with Get call recordings to assemble a complete history for a lead: texts here, calls there.

Overview

Returns messages in your workspace, newest first. Filter by leadId to read the whole conversation with one lead — inbound replies and outbound sends in the same list.

Authentication

Pass your workspace API key as a Bearer token.

Making a request

Query parameters

string
Only messages for this lead — this is how you read a single conversation. 24-character ObjectId hex.
string
Only messages sent from this Tuco line. 24-character ObjectId hex.
string
Match the correlationId returned in a drip 202 ack. Useful for confirming a queued drip became a real message.
number
Page number, 1-based. Default 1.
number
Messages per page. Default 50.

Looking a conversation up by phone number

This endpoint has no phone-number filter. leadId is the only way to scope to one conversation.
To start from a phone number, resolve the lead first, then pass its id:
If you only need the lead’s replies and not the full thread, Get replies accepts recipientPhone directly and skips the lookup.

Response

array
Messages, newest first.
The full stored message document is returned, so you will see fields beyond those listed above — e.g. attachmentUrls, campaignId, correlationId. The fields listed are the ones this endpoint guarantees or adds.
object
A message’s raw attachmentUrls point at private storage and return 403 to an API key. Use attachmentDownloadUrls instead — those are signed and fetchable.
You only ever see messages in your own workspace. The API key you authenticate with determines the workspace; there is no parameter to query another one.

Errors