Discussions

Hello, I'm trying to read the Digital Async Messaging API and I can't find it... <https://developers.avayacloud.com/avaya-experience-platform/reference/senddigitalasyncmessage> <https://developers.avayacloud.com/avaya-experience-platform/reference/getsignedmedia> <https://developers.avayacloud.com/avaya-experience-platform/reference/signedmediadownloaduri>

Are there any recommendations from Avaya side regarding the CORS configuration of the server used for hosting custom widgets? Thanks!

can we integrate chat in wordpress?

Is there any documentation regarding the Orchestration Designer and Workstream Automation for AXP API integration?

I created an Integration and set the routing rule as follows:  My Integration received the following values upon creation: { eventType: 'INTEGRATION_CREATED', providerId: '4faa307b-8ac3-45f3-adca-dba45bf9e5cd', integrationId: 'ee158a2d-3650-4b32-851c-eaf4f65b8f19', integrationName: 'AndrewMessagingIntegration', integrationType: 'custom-messaging-integrations', accountId: 'ELSSRN' } I call Send Async Message and receive this: { messageId: '31c0937d-fe47-4a85-90eb-5e56bc1072de', accountId: 'ELSSRN', status: 'DELIVERED', businessAccountName: 'ee158a2d-3650-4b32-851c-eaf4f65b8f19', customerIdentifiers: { emailAddresses: [ '[email protected]' ] }, channelProviderId: '4faa307b-8ac3-45f3-adca-dba45bf9e5cd', channelId: 'MESSAGING', senderParticipantId: '12345', senderParticipantName: 'Andrew Prokop', senderParticipantType: 'CUSTOMER', body: { elementType: 'text', elementText: { text: 'This is from Postman2', textFormat: 'PLAINTEXT' } }, headers: { sourceType: 'custom-messaging:unknown' }, providerDialogId: '12345', providerSenderId: '12345', receivedAt: '2023-10-09T13:16:58.244448Z', lastUpdatedAt: '2023-10-09T13:16:58.244443Z', correlationId: 'd1cbb607-e09c-4dec-bb61-aa464151487d' } My Orchestration is not invoked and my agent never made aware of the incoming Message. *** ** Avaya response ** We've looked into this issue and for now, you need to consider the providersenderId as a required field while we are working on enhancing the experience to handle blank providersenderId scenario.