Skip to main content
Visit Freshworks.com Visit Freshworks

Hello! I’m currently running into an issue where we’re switching from using the /tickets endpoint to the /search/tickets?query=equery] endpoint. We were previously using the stats.resolved_at field to populate when a ticket was marked as resolved but it seems like we aren’t able to access that field from /search/tickets. 

I know for /tickets we could do include=stats to access the resolved_at field but when trying to apply the same logic to the /search/tickets endpoint, it errored. Does anyone know of another way to access the resolved_at field from the search endpoint? Seems like a very important field to be missing from the Ticket object. 

Hi @kmchuc,

Greetings from Freshworks Community!

I get that you want to add the resolved_at field for ticket search. Only a few parameters are supported in Filter tickets and “resolved_at” is not supported currently. Check out the documentation for the supported fields: https://developer.freshdesk.com/api/#filter_tickets

Hope this helps.

 

Cheers,
Sneha.

Reply


Terms of Use