Create Ticket
Create a new ticket.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Body
A timestamp in RFC 3339 format (e.g., "2025-01-15T01:30:15Z").
"2025-01-15T01:30:15.000Z"
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).
- Email
- Microsoft Teams Dm
- Slack Dm
Optional. Whether AI is active for this ticket. Defaults to false. When true, Serval's AI will respond to messages on this ticket. When false, AI will not respond even if the ticket is at the AI escalation level.
Optional. The type of ticket to create. Defaults to REQUEST. Accepts TICKET_TYPE_REQUEST, TICKET_TYPE_TASK, TICKET_TYPE_INCIDENT, TICKET_TYPE_MAJOR_INCIDENT, TICKET_TYPE_CHANGE, TICKET_TYPE_CUSTOM, TICKET_TYPE_PROBLEM, or TICKET_TYPE_JOURNEY. 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_MAJOR_INCIDENT, TICKET_TYPE_CONVERSATION, TICKET_TYPE_JOURNEY, TICKET_TYPE_INCIDENT, TICKET_TYPE_CHANGE, TICKET_TYPE_CUSTOM, TICKET_TYPE_PROBLEM Represents a workflow relationship on a ticket.
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. Must be a user of the team's organization; deactivated users are allowed, so historical imports can name offboarded employees. API-key and worker callers may name any such user; user-token callers may name someone other than themselves only when they hold the set_ticket_requester permission on the team. On-behalf-of creation is recorded in the org audit log.
Represents a whole or partial calendar date, such as a birthday. The time of day and time zone are either specified elsewhere or are insignificant. The date is relative to the Gregorian Calendar. This can represent one of the following:
- A full date, with non-zero year, month, and day values.
- A month and day, with a zero year (for example, an anniversary).
- A year on its own, with a zero month and a zero day.
- A year and month, with a zero day (for example, a credit card expiration date).
Related types:
- [google.type.TimeOfDay][google.type.TimeOfDay]
- [google.type.DateTime][google.type.DateTime]
- [google.protobuf.Timestamp][google.protobuf.Timestamp]
A timestamp in RFC 3339 format (e.g., "2025-01-15T01:30:15Z").
"2025-01-15T01:30:15.000Z"
Per-language translations. Key = BCP 47 language code, value = translated string.
Optional. The subtype of the ticket (e.g. "normal", "standard", "emergency" for CHANGE tickets). Must correspond to a configured ticket model for the given team and type.
Represents a form relationship on a ticket: the form's submit workflow behaves like a REQUIRED workflow relationship (dependency blocking, auto-close), with the form-engine session as the human gate instead of a workflow-argument form. Retry is NOT supported for form relationships. Creation fails unless the form is deployed, code-first, and its deployed version declares exactly one submit workflow. Mutually exclusive with WorkflowRelationship on the same ticket.
Optional. The svauth group ID to set as the ticket's owning assignment group at creation. Must be one of the team's assignable groups (see ListTicketAssignmentGroups). Incompatible with ai_active — a group-owned ticket is a human queue.
Optional. The ID of the priority option to set on the ticket. Must be one of the team's priority options (see ListPriorities). Defaults to the team's "None" priority.
Response
Success

