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.
Body
Responsible person staff UUIDs. On update, replaces the full assignee list when sent.
Department UUIDs. First department is stored on the main ticket row; all are synced to tickets_departments.
Response
Success
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.
More in Tickets
PATCHUpdate /tickets/{uuid}Still need help? Ask the team