Skip to main content
PATCH
/
v1
/
tickets
/
{ticketId}
/
status
curl --request PATCH \ --url https://api.yo-lead.com/v1/tickets/{ticketId}/status \ --header 'Content-Type: application/json' \ --header 'X-YoLead-Key: <api-key>' \ --header 'X-YoLead-Signature: <api-key>' \ --header 'X-YoLead-Timestamp: <api-key>' \ --data ' { "status": "active", "assigneeId": "64f000000000000000000001" } '
{
  "data": {
    "ticketId": "64f000000000000000000003",
    "chatId": "64f000000000000000000002",
    "oldStatus": "new",
    "newStatus": "active",
    "assigneeId": "64f000000000000000000001"
  }
}

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"

Body

application/json

Ticket status transition.

​
status
enum<string>
required
Available options:
active,
inactive
​
assigneeId
string

MongoDB ObjectId represented as a 24-character hexadecimal string.

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

"64f000000000000000000001"

Response

Ticket status changed.

​
data
object
required