Pesquisas recentes
Sem pesquisas recentes

Nicholas Walsh
Entrou em 09 de mar. de 2022
·
Última atividade em 20 de set. de 2022
Seguindo
0
Seguidores
0
Atividade total
22
Votos
5
Assinaturas
6
VISÃO GERAL DA ATIVIDADE
MEDALHAS
ARTIGOS
PUBLICAÇÕES
COMENTÁRIOS NA COMUNIDADE
COMENTÁRIOS EM ARTIGOS
VISÃO GERAL DA ATIVIDADE
Atividade mais recente por Nicholas Walsh
Nicholas Walsh comentou,
Why is the query string returned to my callback URL with a hash (#) instead of a question mark? Everything after # in the URL will be ignored by the server, so redirecting to a backend script means the query string cannot be parsed.
Exibir comentário · Publicado 20 de set. de 2022 · Nicholas Walsh
0
Seguidores
0
Votos
0
Comentários
Nicholas Walsh criou uma publicação,
Why is the query string from the Chat auth flow returned to my callback URL with a hash (#) instead of a question mark? As anyone who develops enterprise level software should know, everything after # in the URL will be ignored by the server, so redirecting to a backend script means the query string cannot be parsed. What were you guys thinking?
Look at the response sent to the redirect uri here: https://support.zendesk.com/hc/en-us/articles/4408828740762-Chat-API-tutorial-Generating-an-OAuth-token-integrated-Chat-accounts-
Publicado 20 de set. de 2022 · Nicholas Walsh
0
Seguidores
3
Votos
1
Comentário
Nicholas Walsh comentou,
Hi Eric,
I did eventually fix it. The issue was the redirect_uri was http not https. Error description from the API threw me off!
Thanks,
Nick
Exibir comentário · Publicado 31 de mai. de 2022 · Nicholas Walsh
0
Seguidores
0
Votos
0
Comentários
Nicholas Walsh comentou,
Your solution didn't work. Same error.
Exibir comentário · Publicado 30 de mai. de 2022 · Nicholas Walsh
0
Seguidores
0
Votos
0
Comentários
Nicholas Walsh criou uma publicação,
Instructions followed as described here: https://developer.zendesk.com/documentation/live-chat/getting-started/auth/ (which was very difficult to find, by the way!)
Making a POST request to this:
https://www.zopim.com/oauth2/token?grant_type=authorization_code&code=&client_id=&client_secret=&redirect_uri=&scope=read
Code is the code as provided to the redirect_uri in the previous step. An API client is active on the account. Response is as follows:
{
"error": "invalid_grant"
}
What am I doing wrong?
Publicado 18 de mai. de 2022 · Nicholas Walsh
0
Seguidores
2
Votos
4
Comentários
Nicholas Walsh comentou,
I'm looking at the chat "tickets" in the normal Zendesk Support API. Not the Zendesk (Zopim chat) API. Myself and several of our customers have found the assignee_id is specific to Support and doesn't match the agent in the Chat, so in fact it's the other way around to what you're stating. I just wanted to know if it was possible to see the support agent from a chat ticket within the Zendesk Support API. This was to avoid the development cost of creating a completely separate integration for our customers to use Zendesk Chat, but it appears that might be the only solution.
Exibir comentário · Editado 17 de mai. de 2022 · Nicholas Walsh
0
Seguidores
0
Votos
0
Comentários
Nicholas Walsh comentou,
I mean being able to see in the API what Zendesk agent is actually conducting the chat. The assignee_id on chat tickets is incorrect.
Exibir comentário · Publicado 17 de mai. de 2022 · Nicholas Walsh
0
Seguidores
0
Votos
0
Comentários
Nicholas Walsh criou uma publicação,
When viewing tickets through the API that have come via channel "chat" the assignee_id is not the same as the agent in the chat. Is there any way to link the agents in Zendesk Chat with those of Zendesk Support?
Editado 16 de mai. de 2022 · Nicholas Walsh
1
Seguidor
2
Votos
5
Comentários
Nicholas Walsh comentou,
Hi Greg,
Thanks so much for your reply. I've posted on the feedback forum here: https://support.zendesk.com/hc/en-us/community/posts/4452984496922-Suggestion-Ticket-Metrics-improvements
It would be great if something like this could be implemented as it's causing a lot of issues with our customers currently.
Exibir comentário · Publicado 10 de mar. de 2022 · Nicholas Walsh
0
Seguidores
0
Votos
0
Comentários
Nicholas Walsh criou uma publicação,
As mentioned in my comment here: https://support.zendesk.com/hc/en-us/community/posts/4408868005530/comments/4450959974426
Our customers pull data for thousands of tickets a day and require the solved_at and assigned_at values for each one. Retrieving these metrics for each ticket is resulting in issues with rate limiting. It would be very helpful for us to see these values included in the ticket list endpoint data or for us to have the ability to query ticket_metrics by date range.
Publicado 10 de mar. de 2022 · Nicholas Walsh
9
Seguidores
7
Votos
5
Comentários