Skip to main content
tickets

Create /tickets

Create a ticket. Required: subject. Optional: message, client, contact person, email, status, priority, type, assignees, departments, object, project, service, organization, CC fields, tags, react_time_from_client, and custom fields. Returns record with the detail projection.

POST
/tickets
Authorizationstringheaderrequired

API key (Bearer token) created in Setup → API & MCP.

Body

application/json
admininteger

Internal staff creator ID (set automatically on API create).

assigneesstring[]

Responsible person staff UUIDs. On update, replaces the full assignee list when sent.

bcc_emailsstring

BCC email addresses (comma- or semicolon-separated).

cc_contactsstring[]

CC contact person UUIDs.

cc_emailsstring

CC email addresses (comma- or semicolon-separated).

clientstringrequired

Client UUID.

contact_personstring

Contact person UUID.

custom_fieldsobject[]

Custom field values by slug.

departmentsstring[]

Department UUIDs. First department is stored on the main ticket row; all are synced to tickets_departments.

emailstring

Submitter email when no client/contact is linked.

messagestring

Initial ticket message body.

objectstring

Related object UUID.

organizationstring

Organization UUID.

prioritystring

Ticket priority UUID.

projectstring

Related project UUID.

react_time_from_clientstring

Client reaction time (ISO 8601).

servicestring

Ticket service UUID.

statusstring

Ticket status UUID or code_name. Defaults to tenant open status when omitted on create.

subjectstringrequired

Ticket subject.

tagsstring

Comma-separated tag names.

typestring

Ticket type picklist value UUID.

Response

application/json

Success

recordobject

Fields enabled for this documentation instance (projection enabled: feature, option, subdomain, closures) plus account-level form field visibility. Role- and user-level field overrides are not applied here, so an API key whose staff user has such overrides may receive fewer fields. A disabled field is omitted from the response object entirely; a present key with a null value means the record simply has no value.