Create a new ticket in a project. Every field is optional. Common fields include: title, description,
type (BUG, FEATURE_REQUEST, etc.), status, priority, session (contact/session ID
if manually added), and customData (custom fields). Use linkedTickets to reference existing tickets.
sourceTicketId creates the ticket from another one (e.g. a bug from a conversation): it takes that
ticket's contact and company unless session is set, and links both tickets.
priority is a priority key of the ticket's board (LOW, MEDIUM, HIGH or a custom key) or its title; an
unknown value falls back to the board's default priority. GET /projects/ticket-types lists each board's
priorities.
Bearer <token>.Priority key of the ticket's board: LOW, MEDIUM, HIGH or a custom key; the priority's title is also accepted. Each board's priorities are listed by GET /projects/ticket-types.
FEATURE_REQUEST creates run a duplicate guard (409 with the existing request's payload). Pass true to opt out deliberately (e.g. a human already reviewed the suggestions).
Create this ticket from another ticket of the project, e.g. a bug from a customer conversation.
Without a session the new ticket gets the source ticket's contact, and with it the company.
Both tickets are linked. An unknown id, or one of another project, is a 404.
Importing from another helpdesk: the ticket's original creation date (ISO 8601). A date in the past dates the ticket (sorting, reports, retention) and stores it as history: it is read, and no notification, webhook, workflow, SLA or AI agent runs on it. A future date or "now" is ignored.
CRM pipeline entries to link this ticket to. Verified against the project in createTicket — foreign or unknown ids are dropped, never an error. A ticket may sit on several entries at once (one shared task blocking several deals).
Surveys 2.0 response (rsp_…) this ticket follows up on. Verified against
the project in createTicket — an unknown id is dropped, never an error; a
known one is linked both ways, like a reach-out conversation.
Ok