最近の検索
最近の検索はありません

Nicholas Walsh
参加日2022年3月09日
·
前回のアクティビティ2022年9月20日
フォロー中
0
フォロワー
0
合計アクティビティ
22
投票
5
受信登録
6
アクティビティの概要
バッジ
記事
投稿
コミュニティへのコメント
記事へのコメント
アクティビティの概要
さんの最近のアクティビティ Nicholas Walsh
Nicholas Walshさんがコメントを作成しました:
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さんが投稿を作成しました:
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
コメント
Nicholas Walshさんが投稿を作成しました:
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さんがコメントを作成しました:
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さんが投稿を作成しました:
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さんがコメントを作成しました:
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さんが投稿を作成しました:
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
コメント