Export tickets in batch.
Note: If you need more granular exporting options, you can use the /api/mind/tickets endpoint.
Example request for ticket export:
GET /api/mind/export/ticket?limit=1&offset=1&orderByField=t.createdAt&orderByDirection=asc&format=json&filters[0][key]=t.createdAt&filters[0][comparator]=between&filters[0][from]=2023-08-24&filters[0][to]=2026-09-26&filters[1][key]=t.sentiment&filters[1][comparator]=in&filters[1][values][]=neutral
The export is generated immediately when the result set is small enough (≤ 1,000 rows for Excel exports or ≤ 300,000 rows for CSV / JSON). Larger exports are queued asynchronously: the endpoint returns a confirmation message and the file is delivered to the current user’s email address once ready.
The exported columns follow the privacy settings defined by reportingPrivacyLevel.
JWT-based authentication
Export format. Defaults to the backend defaultDateExportFormat setting when omitted.
xlsx, csv, json The number of items to return
1 <= x <= 1000The number of items to skip
x >= 0Column used to order the result set. Must be a column from the reporting_tickets table (for example createdAt, status, secondsToClose).
Sort direction applied to orderByField.
asc, desc Export scheduled or returned successfully.
[
{
"id": 4711,
"channel": "email",
"direction": "in",
"status": "closed",
"priority": "high",
"contractId": "C-1001",
"customerId": "CU-42",
"topic": "Billing",
"subTopic": "Payment reminder",
"incomingMessages": 3,
"outgoingMessages": 2,
"internalMessages": 1,
"manualWorkEntries": 1,
"createdAt": "2024-05-12 09:00:00",
"closedAt": "2024-05-13 16:15:00",
"dueBy": "2024-05-20 09:00:00",
"lastMessageAt": "2024-05-13 16:15:00",
"lastCustomerMessageAt": "2024-05-13 14:22:00",
"secondsSinceLastCustomerMessage": 6780,
"secondsToClose": 116100,
"secondsClosedAfterSLA": -3600
}
]