whoff | 2024-05-20 14:02:02 UTC | #1
I wanted to check this for clarity before we commit to using the API within a workflow, the /consult/external endpoint allows you to kick off a consult call from a data action. Typically, we would expect the consult to require user context (not complaining here), but just want to make sure this wasn't a bug introduced and we will suddenly lose this functionality. https://developer.genesys.cloud/devapps/api-explorer#post-api-v2-conversations-calls--conversationId--participants--participantId--consult-external
we are using this as the request body:
{ "speakTo": "${input.speakTo}", "consultingUserId": "${input.agentUserId}", "address": "${input.address}" }
Is this expected behavior and it won't be reverted in the future?
tim.smith | 2024-05-20 14:15:50 UTC | #2
I would strongly recommend opening a case with Care to get a formal commitment for this behavior. That seems suspect since, as you noted, conversations endpoints typically do require a user context. I would expect this one to follow that pattern. We don't document if a user context or client credentials are allowed/prohibited for API resources, so it's technically an undocumented feature, so it's technically subject to change without notice. Care will be able to open a servops ticket to get formal confirmation on this behavior from the dev team, which will constitute a commitment to that behavior. Or it will result in a bug report, also giving you an answer.
whoff | 2024-05-20 14:35:02 UTC | #3
Thanks Tim, I will open a case.
system | 2024-06-19 14:35:16 UTC | #4
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
This post was migrated from the old Developer Forum.
ref: 26353