Discussions
Send Async Message Required Parameters
Hello,
I am testing the Send Async Message API and I am receiving 201 created responses, with message status DELIVERED, although I do not see that the API is raising interactions in Orchestration.
Although, when I include the keys to the request payload:
"providerSenderId":
"providerDialogId":
"providerMessageId":
"providerParentMessageId"
It is when I finally start flows on Orchestration.
My question is, why does the documentation (<https://developers.avayacloud.com/onecloud-ccaas/reference/senddigitalasyncmessage>) mention that key's (providerSenderId, providerDialogId, providerMessageId, providerParentMessageId) are not required?
Is there some default behavior that I haven't considered when I don't send these keys?
Posted by Uriel Mansilla 10 months ago
Cannot get file upload to work
I call Generate Upload URI and receive this:
{"mediaName":"IMG_2640 (1).jpg","mediaContentType":"image/jpeg","mediaSize":7632,"mediaId":"feaaf9ef-6942-11ee-a296-df21261d0b41","uploadSignedUri":"/v1beta/media/feaaf9ef-6942-11ee-a296-df21261d0b41?ttl=1697148295644&signature=8C60330B78249B7543A493CDE1536BF61068B142B94B107656963DBA8373641F3A1DC19209BFF96908A55E6224A98EA71D941947EFCCF860C84786DE7665"}
I then call Upload Media using this URL:
<https://na.cc.avayacloud.com/api/media-store/v1beta/media/feaaf9ef-6942-11ee-a296-df21261d0b41?ttl=1697148295644&signature=8C60330B78249B7543A493CDE1536BF61068B142B94B107656963DBA8373641F3A1DC19209BFF96908A55E6224A98EA71D941947EFCCF860C84786DE7665>
I receive this in response:
```
data: {
type: 'https://developers.avayacloud.com/onecloud-ccaas/docs/error-handling#constraint-violation',
title: 'Bad Request',
status: 400,
detail: 'provided ttl or signature is not valid',
violations: [Array]
}
```
What am I doing incorrectly? Am I invoking the correct URL?
Posted by Andrew Prokop 11 months ago
Cannot get Send Async Message API to work
I created an Integration and set the routing rule as follows:
![](https://files.readme.io/6ffa8a4-image.png)
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.
Posted by Andrew Prokop 11 months ago