Errors - YoLead Developers

Errors return a stable JSON shape:

{
  "code": 40001,
  "message": "Validation error"
}

Status	Meaning
`400`	Validation or business-rule error.
`401`	Invalid credentials, stale timestamp, or bad signature.
`403`	API key scope is not sufficient, or access is restricted by the current plan.
`404`	Entity does not exist or is not accessible for the API key company.
`409`	Request conflicts with the current entity state.
`500`	Unexpected server error.

Plan restrictions

A valid, correctly signed request can still return 403 when a feature is unavailable on the company’s current plan.

Code	Meaning
`40351`	Public API access is unavailable on the current plan.
`40352`	Starting a new outbound chat is unavailable on the current plan.

State conflicts

Ticket mutations can return 409 if another request changes the chat or ticket while the operation is being processed. Refresh the ticket state before deciding whether to retry.

Code	Meaning
`40972`	The active ticket has no assignee.
`40973`	The stored chat and ticket states are inconsistent.
`40974`	The ticket status changed while the request was being processed.
`40975`	The chat status changed while the request was being processed.
`40976`	The ticket assignee changed while the request was being processed.
`40977`	The chat assignee changed while the request was being processed.