Discussions

Hi, I was tried to start a live chat after entered the first Name, Last Name, and Email. The request header was https\://{HOST-REGION}.api.avayacloud.com/auth/realms/{accountId}/protocol/openid-connect/token with request {grant_type=password&client_id=XX&client_secret=XX&username=XX&password=XX} I checked the response logs was abled to get the response JSON {access token,expires, refresh_expires_in, refresh_token, .....} but get error " Avaya CCaaS Chat SDK [ERROR] ACS-302 : Invalid init parameters." in console. How should I fix this?

I'm writing a custom websocket server using the notification API in Nodejs. I create a new subscription with these options: <br /> `const options = { method: 'POST', headers: { accept: 'application/json', 'content-type': 'application/json', Authorization: Bearer ${this.axpAccessToken}, appkey: this.axpAppKey }, body: JSON.stringify({ "family": "AGENT_ENGAGEMENT", "events": [ "ALL" ], "transport": { "type": "WEBSOCKET" } }) };` and authenticate -> connect. When I start a chat I can see the traffic establishing a connection, but once the chat actually starts nothing is coming through. This happens whether I use a Chat or Async Messaging client and regardless of whether I run the code in NodeJS, or perform the equivalent calls in Postman. I'm requesting ALL events, so why am I not receiving the actual chat messages?

I noticed that the parameters for the sendRichMediaMessage() method seem to have changed at some point. The documentation currently shows the 3rd parameter as an optional callback function (in case of an error). The third parameter used to be a text fallback version of the message to be sent. The documentation page <https://documentation.workspaces.avayacloud.com/widget-framework/docs/api-reference/widget-api/widget-api-methods#sendrichmediamessage> currently shows Version 4.194.5 in the upper right hand corner. Are notifications sent and/or release notes published when changes to the API are made? Is there a way to find out what has changed between the different versions? Cheers, Wilfred

 I have successfully obtained my uploadSignedUri and I now want to upload my attachment. How? the link in the documentation takes you to the "Generate Upload URI" so that's no help. I understand that to upload the attachment i POST multipart/formdata containing the attachment in the mediaFile field. when i do that, i get 400 "the request was rejected because no multipart boundary was found". I have some working code to copy by Andrew Prokop and my non working code it very similar to his. He's using axios, which I believe abstracts some of the handling of formdata and so my pure javascript code is probably missing some details here - what details? this call appears to be completely undocumented. I have tried a number of variations in the call and only succeeded in changing the error message. my code runs client side and i've just picked the file with: x = showOpenFilePicker() off the local disk. i then have: x[0].getFile().then( f=>ulFile( text, f)); and (skipping obtaining the upload URL) in ulFile I have: ``` let formdata = new FormData(); formdata.append( 'mediaFile', f); let ulOpts = { method: 'POST', headers: { 'Content-Type': 'multipart/form-data', 'Accept': 'application/json' }, body: formdata } console.log( "Media Upload to: " + ulObj.uploadSignedUri); console.log( "Media Upload opts: " + JSON.stringify( ulOpts, undefined, 4)); fetch( ulObj.uploadSignedUri, ulOpts).then( r=> r.json()).then( o=> ulFile3( o)); ``` Any ideas??

I have successfully developed a “chat” application using Async Messaging and an intermediary NodeJS service that allows a customer on a website to chat with an agent. When the customer is done they want to end the session. I call Disconnect Dialog: <https://developers.avayacloud.com/avaya-experience-platform/reference/disconnectproviderdialog> which completes successfully but doesn’t end the agent session in Workspaces (as can be achieved using the chat sdk) – it apparently does nothing. Is this the intended behavior, or a bug? If it’s intended – how can I end the agent session? 

according to the release notes drop 67 was supposed to include some additional API calls to allow create and update of engagements. all of drop 67 (and 68)'s content seems to have been delivered into production but I'm not seeing the new APIs in the documentation... were the API changes pulled from the drop? or, is it just the documentation updates lagging behind the software release?

When we try to assign the messaging widget as our main widget for messaging in layout manager it reverts back to chat widget even though AXP administration says successfully saved.

<https://avayaexperienceplatform.github.io/omni-sdk-js/modules/_avaya_axp_client_sdk_core.html> says to import as follows: `import { AxpClientSdk } from '@avaya/axp-client-sdk-core';` when i do that, i get: `Uncaught SyntaxError: Cannot use import statement outside a module` if i add type="module" to my script declaration, i get `Uncaught TypeError: Failed to resolve module specifier "@avaya/axp-client-sdk-core". Relative references must start with either "/", "./", or "../`" if i add "./" in front of "@avaya", i get: `GET http://127.0.0.1:8080/@avaya/axp-client-sdk-core net::ERR_ABORTED 404 (Not Found)` there's some trick to importing these sdks into my application but i can't work it out...

If I create a chat using the chat SDK (v0.1.53), I can successfully call the digital transcript list messages api (passing the engagement ID for the chat from AxP Orchestration). If I call the Digital channel - Engagements get engagement API, passing the same engagement ID, it returns 404 - Engagement not found. Is this the expected behavior? Transcript API sample GET <https://na.api.avayacloud.com/api/digital/transcript/v1/accounts/CRIZWE/engagements/b9a4fab1-3421-4291-a81c-d597368a5b86/messages> returns 200 ok and expected data Get Engagement API sample GET <https://na.api.avayacloud.com/api/digital/channel/v1/accounts/CRIZWE/engagements/b9a4fab1-3421-4291-a81c-d597368a5b86> returns a 404 { "type": "<https://developers.avayacloud.com/onecloud-ccaas/docs/error-handling#resource-not-found">, "title": "Resource Not Found", "status": 404, "detail": "Engagement not found" } Cheers, Wilfred

Hi out there, which API method can be used to insert a message/template into the reply-field of an e-mail? I have tried insertMessageResponse() without luck. It works on chat tho, but not for e-mail.