Bug report - Documentation for /api/v2/conversations/calls/{conversationId}/recordingstate is incorrect

It's not a major issue, but I thought I'd report it anyway

The API Explorer has the return value as:

(unstructured primitive)

(string) Valid values: ACTIVE, PAUSED, NONE.

Whereas in fact it returns {"recordingState":"PAUSED"} or {"recordingState":"ACTIVE"} etc.

Hello,

Could you please create a ticket with Genesys Cloud Customer Care?

The problem appears to be in the API endpoint definition (schema) that we get from Product/Engineering (to automatically generate the SDKs). It is also present on the other recordingstate related endpoints (callbacks, chats, ...).
A ticket via Customer Care is necessary to get this fixed.

Regards,

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.