These docs are for v0.0.1. Click to read the latest docs for v1.0.61.

Discussions

Ask a Question
Back to All

Inconsistent behavour with digital APIs for Chat

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