Create a new ticket.
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
A timestamp in RFC 3339 format (e.g., "2017-01-15T01:30:15.01Z").
Optional. The ID of the parent ticket (this is a special relationship type)
Note that these are ADDITIONAL sync targets. There may be some "default" sync targets for the team (e.g. ServiceNow, JSM etc).
Optional. Whether AI is active for this ticket. Defaults to false. When true, users can chat with Serval for assistance on this ticket.
Optional. The type of ticket to create. Defaults to REQUEST. If parent_ticket_id is set, this must be TASK (or omitted, in which case TASK is used).
TICKET_TYPE_UNSPECIFIED, TICKET_TYPE_REQUEST, TICKET_TYPE_TASK, TICKET_TYPE_INCIDENT, TICKET_TYPE_CONVERSATION, TICKET_TYPE_JOURNEY Optional. A workflow to associate with this ticket. The workflow will show a form to collect inputs, then run when the user fills the form.
Optional. Relationships to create with other tickets. For example, to indicate this ticket depends on another ticket.
Optional. The ID of the user this ticket is created on behalf of (the requester). Defaults to created_by_user_id if not provided. Use this when creating a ticket on behalf of someone else, e.g., when creating child tasks in a journey where the requester should be the journey's requester.
Optional. Due date (date only, no time component).
Success