API 500 Server Error | The place for Zendesk users to come together and share
Skip to main content

API 500 Server Error

  • December 19, 2024
  • 33 replies
  • 51 views

Show first post

33 replies

Bruno13
  • Author
  • April 1, 2025

Hi Samantha, thank you dearly for the reply.

 

I understand that it is still in EAP and that we don't have a timeline for a solution.


You mentioned some internal comments, do you by any chance have any further feedback that we could work on?

We appreciate any guidance.

Thank you !


Samanta Velho
  • Product Manager
  • April 1, 2025
Hi Bruno
 
Thank you for your understanding and patience.
 
The internal comment mentioned was on March 10th, and it was to inform you and your team that we were changing the ownership of this issue. We believe the root cause may lie in another area, and we are currently actively investigating the matter. Additionally, we have received similar complaints from a couple of other customers, and we are working diligently to find a solution.
 
I hope to have more updates to share with you soon. Your guidance and feedback are greatly appreciated.
 
Thank you!
 
Best regards,
 
Samantha

Bruno13
  • Author
  • April 4, 2025

Sounds good, thank you Samantha!
 

I have update here just to share the current error I'm facing:

403 Client Error: Forbidden for url: https://rebuy.zendesk.com/wfm/public/api/v1/reports/788f1bdb-e128-40ce-b985-d973b1e6a2e1/data?startTime=1742860800&endTime=1742860800&page=10

 

Thanks again!


Samanta Velho
  • Product Manager
  • April 4, 2025
Thanks, Bruno, for your understanding and follow-up!
 
I'm sharing the details provided with our engineering team.
 
Have a great weekend!
 
Best,
 
Samanta

Samanta Velho
  • Product Manager
  • April 9, 2025
Hello,
 
I wanted to provide an update regarding the 403 (Forbidden) errors that have been reported with our API.
 
We have allocated engineering resources to investigate the issue further. Our enhanced logging has revealed that the problem is likely related to how API requests are handling scopes. We are currently working on a fix and expect to implement it between today and tomorrow. However, please note that this fix will not be available in production immediately, as we are dependent on our release cycle. We anticipate that it will be deployed during the week of the 21st.
 
We appreciate your patience as we work through this, and we will keep you updated on our progress. If you have any further questions or concerns, please feel free to reach out.
 
Best regards,
Samanta

Samanta Velho
  • Product Manager
  • April 11, 2025
Hello,
 
I’m reaching out to provide an important update regarding the 403 (Forbidden) errors that have been reported with our API.
I’m pleased to inform you that we successfully implemented a fix yesterday, and the issue related to the 403 error should no longer be experienced.
 
We kindly ask that you test on your side and let us know if everything is functioning properly.
 
Thank you for your patience and understanding throughout this process.
If you have any further questions or concerns, please feel free to reach out.
 
Best regards,
 
Samanta

Bruno13
  • Author
  • April 11, 2025

Hi Samanta,

 

Those are great news!

I've noticed an improvement, yes!

I will keep you posted in case we see further errors.

Thank you so much for the effort and support.

 

Best,

Bruno


Samanta Velho
  • Product Manager
  • April 16, 2025
Hi Bruno,
 
I will solve this topic for now, but feel free to reopen it or create a follow in case you need.
 
 
Regards,
Samanta