Filter tickets API not returning link header

[zpaine]

Hello,

The FreshService API endpoint that gets tickets with filtering is not returning the “link” header to the next page. This should be returned as per the documentation on pagination:
https://api.freshservice.com/#pagination

Other people have had this issue as well:

API Not Returning "Link" In Header

​ Hi, I am probably missing the obvious, so go easy on me! We are fairly new to Fresh, and I am trying to pull back all the tickets this month using the API (via Python). But it has pulling only 30 tickets. As this is a nice clean number, I was assuming pagination, however looking in the headers there is no “Link”. I am expecting about 1300 rows to be returned for this month. The URL/Query being used… https://domain-here.freshservice.com/api/v2/tickets/filter?query="created_at:>'2023-01-31…

Other endpoints may be effected as well:

Custom Object Records: Filter Pagination

See some folks that have asked similar questions, but do not see an solutions listed: Pagination in Freshservice Custom Objects API is not working - Product - Freshworks Developer Community When I get the custom object records by custom object id, there is the Headers.Link to perform pagination. However, if I do a call like this: https://{{fs_base_url}}.freshservice.com/api/v2/objects/21000011818/records?query=category_dd1 : ‘Hardware’&page=1 There is no Headers.Link. Even manually paging…

I’ve tested calls that definitely have more pages, because for one I can specify the next page and get more data, and for two because the body is returning a field named “total” that specifies 100s - 1000s of objects.

Examples

Get https://company.freshservice.com/api/v2/tickets/filter?query="tag:'Some Tag'"

Get https://company.freshservice.com/api/v2/tickets/filter?query="tag:'Some Tag' AND created_at:>'2023-08-01' AND created_at:<'2024-02-01'"

[Bene_Immanuel (Benny Immanuel)]

Hi @zpaine

Welcome to the community!

You can use the per_page and page query parameters to iterate through the pages.

As of now, this will be a relevant solution because I have used these endpoints and don’t recall the links in the response.

Let me know if you have any questions.

[DougAtBHB (Doug Horton)]

This is the only way I have been able to do this.

[zpaine]

I understand the workaround, but the engineers should still fix these endpoints! Do these community topics make it to them?

[Bene_Immanuel (Benny Immanuel)]

Yeah!

Thank you for being part of our community and sharing your ideas! Just wanted to let you know that we’ve got a solid community here and our product engineers are always keeping an eye on the posts.

If you tag them, the product engineers will be happy to jump in, prioritize your questions, and provide a solution. If the ideas or bugs you present are legit and valid, they’ll dive deep, brainstorm, debug, and either fix the issue or add the feature you’re asking for. They’ll include your request in the roadmap and give you an estimation if possible.

Keep those suggestions coming, and feel free to reach out if you have any more questions or need anything else.

[zpaine]

Thanks, how do you tag the product engineers?