GET/desk/api/v2/tickets/pagination.json
Allows you to get pagination for tickets separately in some circumstances
where performance may be a concern. The same parameters should be used for consistency as were used with the listing request.
The following values are allowed in the [filter](/docs/desk/d667a6937d077-filtering-api-results) query parameter:
- id
- subject
- previewText
- originalRecipient
- responseTimeMins
- resolutionTimeMins
- happinessSurveySentAt
- spam_score
- spam_rules
- customer
- contact
- inbox
- agent
- status
- priority
- source
- type
- businesshours
- company
- createdAt
- updatedAt
- deletedAt
- updatedBy
- deletedBy
- state
Responses
- Code
- 200
- Type
- object
- Schema
- Description
- 200 OK
Pagination handles response pagination
- Code
- 400
- Type
- object
- Schema
- Description
- 400 Bad Request
Validator hold the validation errors. Typically you shouldn't create this directly but use the New() function.
200 OK
Pagination
{
"count": 0,
"hasMore": true,
"hasMorePages": true,
"page": 0,
"pageOffset": 0,
"pageSize": 0,
"pages": 0,
"records": 0
}