Recent searches
No recent searches

Terry Sue
Joined Nov 20, 2024
·
Last activity Dec 02, 2024
Following
0
Followers
0
Total activity
3
Votes
0
Subscription
1
ACTIVITY OVERVIEW
BADGES
ARTICLES
POSTS
COMMUNITY COMMENTS
ARTICLE COMMENTS
ACTIVITY OVERVIEW
Latest activity by Terry Sue
Terry Sue commented,
Thanks that works!
Is updated_at the only supported sort field? I've tried created_at but get the following error
{
"error": "InvalidPaginationParameter",
"description": "sort is not valid"
}
View comment · Posted Dec 02, 2024 · Terry Sue
0
Followers
0
Votes
0
Comments
Terry Sue created a post,
Hi,
I'm using the List Requests API as documented here: https://developer.zendesk.com/api-reference/ticketing/tickets/ticket-requests/#list-requests
When I use cursor pagination and attempt to sort the request the response is not sorted. If I make the same request with offset pagination it sorts fine.
The documentation mentions that the sort operations are supported and makes no mention of pagination types affecting the sort operations; it even recommends using cursor pagination over offset pagination.
Here's the request I'm making: {{baseUrl}}/api/v2/requests.json?sort_by=updated_at&sort_order=desc&page[size]=5
And the response with only the relevant data:
{
"requests": [
{
"updated_at": "2024-11-06T16:15:28Z"
},
{
"updated_at": "2024-11-06T16:17:21Z"
},
{
"updated_at": "2024-11-06T16:14:44Z"
},
{
"updated_at": "2024-11-01T20:12:45Z"
},
{
"updated_at": "2024-11-15T22:23:45Z"
}
],
"meta": {
"has_more": true,
"after_cursor": "...",
"before_cursor": "..."
}
}
As you can see the updated_at fields are in random order. Changing the sorting field does not change the order of the response in any way.
Is the documentation not accurate? Or is this a bug?
Posted Nov 20, 2024 · Terry Sue
0
Followers
3
Votes
2
Comments