最近搜索


没有最近搜索

Nicholas Walsh's Avatar

Nicholas Walsh

已加入2022年3月09日

·

最后活动2022年9月20日

关注

0

关注者

0

活动总数

22

投票

5

订阅

6

活动概览

的最新活动 Nicholas Walsh

Nicholas Walsh 进行了评论,

评论Setting up Zendesk Chat

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.

查看评论 · 已于 2022年9月20日 发布 · Nicholas Walsh

0

关注者

0

投票

0

评论


Nicholas Walsh 创建了一个帖子,

帖子 Feedback - Chat and Messaging (Chat)

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-

已于 2022年9月20日 发布 · Nicholas Walsh

0

关注者

3

投票

1

Comment


Nicholas Walsh 进行了评论,

社区评论 Developer - Zendesk APIs

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

查看评论 · 已于 2022年5月31日 发布 · Nicholas Walsh

0

关注者

0

投票

0

评论


Nicholas Walsh 进行了评论,

社区评论 Developer - Zendesk APIs

Your solution didn't work. Same error.

查看评论 · 已于 2022年5月30日 发布 · Nicholas Walsh

0

关注者

0

投票

0

评论


Nicholas Walsh 创建了一个帖子,

帖子 Developer - Zendesk APIs

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?

已于 2022年5月18日 发布 · Nicholas Walsh

0

关注者

2

投票

4

评论


Nicholas Walsh 进行了评论,

社区评论 Developer - Zendesk APIs

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.

查看评论 · 已于 2022年5月17日 编辑 · Nicholas Walsh

0

关注者

0

投票

0

评论


Nicholas Walsh 进行了评论,

社区评论 Developer - Zendesk APIs

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.

查看评论 · 已于 2022年5月17日 发布 · Nicholas Walsh

0

关注者

0

投票

0

评论


Nicholas Walsh 创建了一个帖子,

帖子 Developer - Zendesk APIs

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?

已于 2022年5月16日 编辑 · Nicholas Walsh

1

关注者

2

投票

5

评论


Nicholas Walsh 进行了评论,

社区评论 Developer - Zendesk APIs

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.

查看评论 · 已于 2022年3月10日 发布 · Nicholas Walsh

0

关注者

0

投票

0

评论


Nicholas Walsh 创建了一个帖子,

帖子 Feedback - Ticketing system (Support)

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.

已于 2022年3月10日 发布 · Nicholas Walsh

9

关注者

7

投票

5

评论