Skip to main content
The Tickets API gives you full programmatic control over every support ticket in your FusionDesk workspace. Use it to automate triage workflows, sync ticket state with external systems, bulk-import historical cases, or build custom dashboards — all over standard HTTPS with JSON bodies.
All requests must include the Authorization: Bearer fd_live_xxxxxxxxxxxxxxxxxxxx header. Requests without a valid API key return 401 Unauthorized.

GET /tickets

Retrieve a paginated list of tickets across your workspace. Apply query parameters to narrow results by status, priority, or assignee.
string
Filter by ticket status. Accepted values: open, in_progress, resolved, closed.
string
Filter by priority level. Accepted values: low, medium, high, urgent.
string
Return only tickets assigned to the specified user ID.
integer
default:"1"
Page number for paginated results.
integer
default:"25"
Number of tickets per page. Maximum value is 100.
array
Array of ticket objects matching the applied filters.
integer
Current page number.
integer
Number of results per page.
integer
Total number of tickets matching the query.

POST /tickets

Create a new support ticket in your workspace. You must supply a subject and description; all other fields are optional and fall back to sensible defaults.
string
required
A concise summary of the issue. Maximum 255 characters.
string
required
Full details of the issue. Supports plain text or Markdown.
string
default:"medium"
Priority level for the ticket. Accepted values: low, medium, high, urgent.
string
ID of the agent to assign the ticket to on creation. Leave blank to create an unassigned ticket.
array
Array of tag strings to attach to the ticket (e.g., ["billing", "urgent-customer"]).
object
The newly created ticket object. See the field definitions under GET /tickets for details.
After creating a ticket, you can immediately update its SLA target or link it to a project using the respective API endpoints.

GET /tickets/{id}

Fetch the full details of a single ticket by its unique ID.
string
required
The unique ticket ID (e.g., tkt_01HZ8MXKPQ3R7VWYTBN6CDSF).
object
Full ticket object for the requested ID. Returns 404 Not Found if the ticket does not exist or belongs to a different workspace.

PUT /tickets/{id}

Update one or more fields on an existing ticket. Only the fields you include in the request body are changed; omitted fields retain their current values.
string
required
The unique ID of the ticket to update.
string
Updated summary of the issue.
string
Updated full description of the issue.
string
New priority level. Accepted values: low, medium, high, urgent.
string
New status. Accepted values: open, in_progress, resolved, closed.
string
ID of the agent to reassign the ticket to. Pass null to unassign.
array
Full replacement list of tags. This overwrites the existing tag array.
object
The full, updated ticket object reflecting all applied changes.

DELETE /tickets/{id}

Permanently delete a ticket and all associated data. This action is irreversible.
string
required
The unique ID of the ticket to delete.
A successful deletion returns 204 No Content with an empty response body.
Deleting a ticket is permanent and cannot be undone. All comments, attachments, and activity history associated with the ticket are also removed. If you need to preserve the record, update the ticket’s status to closed instead.