Get List of Tickets
GET /tickets/
URL Example
https://system_domain/api/v2/tickets/?page=1&search=John Doe
Query Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
page | number | No | Page number (30 tickets are displayed per page) |
search | string | No | Search across tickets |
exact_search | number | No | Search for exact match of the "search" value (1 - exact match, 0 - standard search) |
pid | number | No | Search for tickets by parent ticket ID |
source_list | string | No | Search for tickets by source (Sources are separated by commas, e.g.: api,system) |
user_list | string | No | Search for tickets by owner ID (IDs are separated by commas) |
owner_list | string | No | Search for tickets by ticket assignee ID (IDs are separated by commas) |
department_list | string | No | Search for tickets by ticket department ID (IDs are separated by commas) |
status_list | string | No | Search for tickets by ticket status ID (IDs are separated by commas) |
priority_list | string | No | Search for tickets by ticket priority ID (IDs are separated by commas) |
type_list | string | No | Search for tickets by ticket type ID (IDs are separated by commas) |
freeze | number | No | Filter for frozen tickets (1 - only frozen tickets, 0 - only active tickets; default: all tickets) |
deleted | number | No | Filter for deleted tickets (1 - only deleted tickets, 0 - all tickets, default) |
from_date_created | string | No | Creation date "from". Tickets created since the specified moment (YYYY-MM-DD HH:MM:SS) |
to_date_created | string | No | Creation date "to". Tickets created before the specified moment (YYYY-MM-DD HH:MM:SS) |
from_date_updated | string | No | Update date "from". Tickets with changes made since the specified moment (YYYY-MM-DD HH:MM:SS) |
to_date_updated | string | No | Update date "to". Tickets with changes made before the specified moment (YYYY-MM-DD HH:MM:SS) |
order_by | string | No | Sort tickets, comma-separated. Available parameters: date_created, date_updated, viewed_by_staff, viewed_by_client. Sort order: {asc} - ascending and {desc} - descending; Default value - date_created{desc} |
Response Example
{
"data": {
"1": {
"id": 1,
"pid": 0,
"unique_id": "ABC-123",
"date_created": "2025-11-21 06:41:58",
"date_updated": "2025-11-21 06:41:58",
"title": "Ticket Subject",
"source": "system",
"status_id": "open",
"priority_id": 1,
"type_id": 0,
"department_id": 1,
"department_name": "Support Department",
"owner_id": 0,
"owner_name": "",
"owner_lastname": "",
"owner_email": "",
"user_id": 1,
"user_name": "test",
"user_lastname": "",
"cc": [],
"bcc": [],
"followers": [],
"ticket_lock": 0,
"sla_date": "21.11.2025 06:51",
"sla_flag": 1,
"freeze_date": null,
"freeze": 1,
"viewed_by_staff": 1,
"viewed_by_client": 0,
"rate": "",
"rate_comment": "",
"rate_date": "",
"deleted": 0,
"custom_fields": [],
"tags": [],
"jira_issues": []
},
"2": {
"id": 2,
"pid": 0,
"unique_id": "ABC-124",
"date_created": "2025-11-21 07:17:40",
"date_updated": "2025-11-21 07:17:40",
"title": "Ticket Subject 2",
"source": "system",
"status_id": "open",
"priority_id": 1,
"type_id": 0,
"department_id": 1,
"department_name": "Support Department",
"owner_id": 0,
"owner_name": "",
"owner_lastname": "",
"owner_email": "",
"user_id": 2,
"user_name": "test2",
"user_lastname": "",
"cc": [],
"bcc": [],
"followers": [],
"ticket_lock": 0,
"sla_date": null,
"sla_flag": 0,
"freeze_date": null,
"freeze": 1,
"viewed_by_staff": 1,
"viewed_by_client": 0,
"rate": "",
"rate_comment": "",
"rate_date": "",
"deleted": 0,
"custom_fields": [],
"tags": [],
"jira_issues": []
}
},
"pagination": {
"total": 2,
"per_page": 30,
"current_page": 1,
"total_pages": 1
}
}
info
Information about some ticket parameters returned by the GET /tickets/ and GET /tickets/:ticket_id/ methods may differ.
It is recommended to use the GET /tickets/:ticket_id/ method if you need to get the most up-to-date data for a specific ticket.
The GET /tickets/ method uses indexed data, which may be updated with a delay.