Recent searches
No recent searches
I can't use endpoint /v1/activities
Posted Apr 11, 2024
When we try to use endpoint /v1/activities we are getting the error below:
Request URL: https://DOMAIN.zendesk.com/wfm/public/api/v1/activities?startTime=1709262000,
Response Code: 500, Response Text: {"success":false,"message":"Unexpected error occurred"}When we try to use the endpoint /v1/reports/{templateId}/data it is returning data, but in the endpoint /v1/activities so far it only returns the above error. Our request is as follows (but without the internal data).
curl --location 'https://DOMAIN.zendesk.com/wfm/public/api/v1/activities?startTime=1709262000' \
--header 'Authorization: Basic BASE64_ENCODED' \
--header 'Cookie: __cfruid=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX'Is the /v1/activities API really working or are we doing something wrong?
0
7
7 comments
Samanta Velho
Hi again Jessica!
Thank you for bringing this issue to our attention regarding the /v1/activities endpoint.
Upon investigating your query, we've identified that the error arises because the current version of the endpoint does not handle non-active or deleted agents. These agents should ideally be included in the responses, but they are currently omitted, leading to unexpected errors.
We understand the importance of having comprehensive data access, including both active and non-active agents. Therefore, we are actively working to update this endpoint to incorporate non-active and deleted agents into the response data. This enhancement will ensure that you receive complete and accurate information, aligning with your operational needs.
We appreciate your patience as we work on this improvement, and we will keep you updated on our progress.
0
Samanta Velho
Hi again Jessica!
Just to let you know that we deployed a fix this morning and that now you should be able to properly use the endpoint.
Please let me know if that's not the case.
Thank you again for your patience while we were working to solve this issue.
0
Jessica
Hi Samanta!
The fix didn't work as we're getting the same error as before.
0
Samanta Velho
Thanks for the feedback!
We are again checking the code that was deployed.
I'll keep you posted.
0
Samanta Velho
Hi Jessica!
Just got feedback from the team that a new fix for the issue has been deployed. Could you please check on your side if everything is now working properly? Thank you for your patience with this fix. Please feel free to reach out if there are still any persistent issues.
Thanks!
1
Jessica
Thanks! It's working properly now!
0
Samanta Velho
Amazing! Thank you so much for letting me know!
0