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

Lachlan Kidson
参加日2024年6月04日
·
前回のアクティビティ2024年7月01日
フォロー中
0
フォロワー
0
合計アクティビティ
8
投票
2
サブスクリプション
1
アクティビティの概要
バッジ
記事
投稿
コミュニティへのコメント
記事へのコメント
アクティビティの概要
さんの最近のアクティビティ Lachlan Kidson
Lachlan Kidsonさんがコメントを作成しました:
Thanks Erica, do you know if there are any examples of this anywhere? Our attempts resulted in getting a 500 error back from the server. It's not too clear how to express that the payload is multipart/form-data when using request()
コメントを表示 · 投稿日時:2024年6月28日 · Lachlan Kidson
0
フォロワー
0
投票
0
コメント
Lachlan Kidsonさんがコメントを作成しました:
Having looked at this a bit further it seems like the expected approach is to upload an attachment via
https://developer.zendesk.com/api-reference/ticketing/side_conversation/side_conversation_attachment/, retrieve the UUID from the response - and then use this in the payload for creating the side conversation.
Is it possible to perform the upload via ZAFClient's request method?
コメントを表示 · 投稿日時:2024年6月20日 · Lachlan Kidson
0
フォロワー
0
投票
0
コメント
Lachlan Kidsonさんが投稿を作成しました:
I am part of a team developing an application installed to the ticket_sidebar
location. As part of this we want to be able to programatically create side conversations for our users.
We've had success doing by calling the side conversations API via ZAFClient
:
Our code is essentially this, which works:
const { 'ticket.id': id } = (await client.get(
'ticket.id',
));
const message = {
"message": {
"subject": "My printer is on fire!",
"body": "The smoke is very colorful.",
"to": [
{ "email": "someone@example.com" }
],
}
};
await client.request({
contentType: 'application/json',
url: `/api/v2/tickets/${id}/side_conversations`,
type: 'POST',
data: JSON.stringify(message),
dataType: 'json',
})
We would also like the ability to add attachments. This is where we run into issues.
The example code from the documentation would suggest this is possible:
{
"message": {
"subject": "My printer is on fire!",
"body": "The smoke is very colorful.",
"to": [
{ "email": "someone@example.com" }
],
"attachment_ids": ["0123456789"]
},
However the attachment_ids
field is not documented on the associated Message
object, and in testing always results in an error that the attachment was not found.
Our expectation was that we could get a list of attachments by first making a request to /api/v2/tickets/${id}/comments.json
, then use the attachment IDs from that as part of the message payload. (We've also confirmed work with the api/v2/attachments/
endpoint). Inspecting the GraphQL network requests that are made when creating a side conversation via the UI also results in the same attachment IDs being used - so it is unclear why these attachments aren't being found.
TL;DR - is the attachment_ids
field actually supported in the side conversations API, and if so what do we need to do to get this to work?
投稿日時:2024年6月10日 · Lachlan Kidson
1
フォロワー
5
投票
8
コメント