Documentation Index
Fetch the complete documentation index at: https://mintlify.com/pixlcore/xyops/llms.txt
Use this file to discover all available pages before exploring further.
Overview
The Tickets API provides endpoints for creating, updating, searching, and managing support tickets within xyOps.Get Ticket
GET /api/app/get_ticket/v1
Load a single ticket by ID or ticket number.
Parameters
Ticket ID (either id or num required)
Ticket number (alternative to id)
Example
cURL
Response
Get Multiple Tickets
POST /api/app/get_tickets/v1
Fetch information about multiple tickets.
Parameters
Array of ticket IDs
If true, include full details including body and changes (default: false)
Example
cURL
Search Tickets
POST /api/app/search_tickets/v1
Search for tickets using query syntax.
Parameters
Search query (default:
* for all)Pagination offset (default: 0)
Results per page (default: 1)
Sort field (default:
_id)Sort direction:
-1 descending, 1 ascendingIf true, scrub verbose params from results
Example
cURL
Response
Create Ticket
POST /api/app/create_ticket/v1
Create a new ticket. Requires the create_tickets privilege.
Parameters
Ticket subject/title
Ticket description (Markdown supported)
Ticket type (e.g.,
task, bug, feature)Status (default:
open)Array of assigned usernames
Array of tag IDs
Due date as Unix timestamp
Array of CC’d email addresses
Auto-generate body from template:
job or alertJob ID (when using
template: "job")Alert invocation ID (when using
template: "alert")Example
When using
template: "job" or template: "alert", the ticket body is auto-generated from the corresponding job or alert data.Update Ticket
POST /api/app/update_ticket/v1
Update an existing ticket. Requires the edit_tickets privilege. Supports sparse updates.
Parameters
Ticket ID to update
Any ticket properties to update (subject, status, assignees, etc.)
Example
cURL
Add Ticket Change
POST /api/app/add_ticket_change/v1
Add a change (comment) to a ticket. Requires the edit_tickets privilege.
Parameters
Ticket ID
Change object with
type and optional bodyExample
Update Ticket Change
POST /api/app/update_ticket_change/v1
Update or delete a specific change in a ticket. Requires the edit_tickets privilege.
Parameters
Ticket ID
Change ID to update or delete
Updated change properties (omit if deleting)
If true, delete the change
Example
cURL
Upload Ticket Files
POST /api/app/upload_user_ticket_files/v1
Upload files for a ticket. Requires the edit_tickets privilege.
Parameters
Ticket ID
If true, immediately attach files to ticket
Request Format
Usemultipart/form-data with file fields.
Example
cURL
Response
Delete Ticket File
POST /api/app/delete_ticket_file/v1
Delete a file from a ticket. Requires the edit_tickets privilege.
Parameters
Ticket ID
File path to delete
Example
cURL
Delete Ticket
POST /api/app/delete_ticket/v1
Permanently delete a ticket. Requires the delete_tickets privilege.
Parameters
Ticket ID to delete
Example
cURL
Ticket Types
Common ticket types:| Type | Description |
|---|---|
task | General task or to-do |
bug | Software defect |
feature | Feature request |
question | Question or inquiry |
incident | Service incident |
Ticket Statuses
Common ticket statuses:| Status | Description |
|---|---|
draft | Not yet published |
open | Open and unassigned |
in_progress | Currently being worked on |
on_hold | Waiting for external input |
resolved | Completed successfully |
closed | Archived/closed |
Change Types
Ticket changes track history:| Type | Description |
|---|---|
change | System-generated change record |
comment | User comment |
status | Status change |
assignment | Assignment change |
Ticket body and comments support Markdown formatting.