Skip to main content
PATCH
/
v1
/
tickets
/
{ticketId}
/
assignee
Change ticket assignee
curl --request PATCH \
  --url https://api.yo-lead.com/v1/tickets/{ticketId}/assignee \
  --header 'Content-Type: application/json' \
  --header 'X-YoLead-Key: <api-key>' \
  --header 'X-YoLead-Signature: <api-key>' \
  --header 'X-YoLead-Timestamp: <api-key>' \
  --data '
{
  "newAssigneeId": "64f000000000000000000004"
}
'
{
  "data": {
    "ticketId": "64f000000000000000000003",
    "chatId": "64f000000000000000000002",
    "previousAssigneeId": "64f000000000000000000001",
    "newAssigneeId": "64f000000000000000000004"
  }
}

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 assignee change.

​
newAssigneeId
string
required

MongoDB ObjectId represented as a 24-character hexadecimal string.

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

"64f000000000000000000001"

Response

Ticket assignee changed.

​
data
object
required