Skip to main content
Visit Freshworks.com Visit Freshworks

I just started using the API so perhaps it’s my own naivety.

When I hit the endpoint to get paged records:
https://{company}.freshservice.com/api/v2/objects/1337/records, the next_page_link is to another company’s production instance?  

Also, you guys misspelled the sort_order query parameter in the documentation: https://api.freshservice.com/#list_all_custom_object_records

It would also help if you specified the max value for page_size. 

Hi @alyssia.correa and @Kamakshi V 

This is a FreshService inquiry on the FreshDesk forum.

 

Regards,

Hi @Dev1 

All of these can be considered bugs, not been able to be handled by Users/Community member.

I’d suggest for this to submit a support case. Well, actually, 3 cases, because you’re reporting 3 different topics, so, support can offer better tracking for your for them.

 

Regards,

Hi,

It sounds like there might be a misconfiguration on the server side that's returning the incorrect `next_page_link`. This could be due to an issue with the API itself or how it's set up for your instance. I'd recommend reaching out to Freshservice support with details of the issue.

Regarding the misspelling of the `sort_order` query parameter in the documentation, that's a good catch! I'd suggest reporting this to their documentation team so they can correct it.

For the `page_size`, while it's often 100 by default in many APIs, the max value can vary. It's best to confirm this with Freshservice directly or check if the API returns an error when an excessively large `page_size` is used.

Hope this helps!

Reply


Terms of Use