Skip to main content
Question

Issue: Ember Data Request GET /api/_/collaboration/threads returned a 404 Payload (application/json) [object Object]

  • August 5, 2023
  • 8 replies
  • 632 views

I am on a free trial and i keep getting this error, what am i doing wrong?

Error: Ember Data Request GET /api/_/collaboration/threads returned a 404 Payload (application/json) [object Object]

 

It always shows up when i view tickets.

 

Thanks all

 

 

8 replies

Daniel Söderlund
Top Contributor ⭐
Forum|alt.badge.img+14

Could it be a app you have installed? The path doesn't look correct . 


Ulas
Community Debut
  • Community Debut
  • November 3, 2023

Hi,

 

i get the same Error Massage in the freshdesk.com webview, so it cant be a problem with a installation.

 

 


PeterK
Community Debut
  • Community Debut
  • April 8, 2024

We are seeing the the same issues on a number of ticket but not all

 

any feedback on this ?


alyssia.correa
Forum|alt.badge.img+8

Hello folks, I see this still isn’t resolved, tagging @hemanth.ramya to support please!


hemanth.ramya
Community Manager
Forum|alt.badge.img+9
  • Community Manager
  • September 16, 2024

Hello everyone,

 

Greetings from Freshworks Community. :)

 

We apologize for the delay in getting back here. Can you please confirm if the issue still persists as of today? In this case, can you please confirm if this specifically happens when you log in to Freshdesk via the custom portal URL and access a ticket with a thread, throwing a 404 error as shown in the screenshot shared?


Looking forward to hearing from you. 

 

Cheers, 


Servcomm
Community Debut
  • Community Debut
  • July 21, 2025

We are getting this error as well, more and more frequently and it’s still persists as of today


Forum|alt.badge.img
  • Apprentice
  • July 30, 2025

Just did some googling to try and troubleshoot this problem as it has now appeared on our freshdesk installation too. This perhaps points to the issue being on freshdesk’s end?


  • Community Debut
  • July 30, 2025

I’ve run into a similar 404 error before during a trial it turned out to be related to accessing tickets through a custom portal. Might be worth checking if the URL you’re using is correct or if there are any missing permissions. Hope it gets sorted soon.