Skip to main content
GET
/
v1
/
tickets
/
{ticketId}
/
history
Get ticket history
curl --request GET \
  --url https://api.yo-lead.com/v1/tickets/{ticketId}/history \
  --header 'X-YoLead-Key: <api-key>' \
  --header 'X-YoLead-Signature: <api-key>' \
  --header 'X-YoLead-Timestamp: <api-key>'
{
  "data": {
    "ticket": {
      "id": "64f000000000000000000003",
      "chatId": "64f000000000000000000002",
      "status": "active",
      "assigneeId": "64f000000000000000000001",
      "startedAt": "2026-05-08T11:00:00.000Z"
    },
    "messages": [
      {
        "id": "wamid.HBg...",
        "sentAt": "2026-05-08T11:01:00.000Z",
        "fromId": "15551234567",
        "direction": "incoming",
        "text": "Hello",
        "attachments": []
      }
    ],
    "nextChunkStartMessageId": "wamid.HBg..."
  }
}

Documentation Index

Fetch the complete documentation index at: https://docs.yo-lead.com/llms.txt

Use this file to discover all available pages before exploring further.

Authorizations

​
X-YoLead-Key
string
header
required

Public API key generated in the YoLead UI.

​
X-YoLead-Timestamp
string
header
required

Unix timestamp in milliseconds. Requests must be signed within a 5-minute window.

​
X-YoLead-Signature
string
header
required

Hex HMAC-SHA256 signature over <timestamp>.<raw_body> using the API secret.

Path Parameters

​
ticketId
string
required

Ticket id. MongoDB ObjectId represented as a 24-character hexadecimal string.

Pattern: ^[0-9a-fA-F]{24}$
Example:

"64f000000000000000000001"

Query Parameters

​
chunkLastMessageId
string

Cursor returned as nextChunkStartMessageId by the previous history response.

Minimum string length: 1

Response

Ticket history.

​
data
object
required