Description
We will make changes to both the PostTextRequest and PostTextResponse contracts in the Textbots API. These are affected because they both use the PostTextMessage contract, and the content array is changing..
The content array of MessageContent will switch to a different model. The fields being removed are not supported by the backend service that handles this request. Within MessageContent, the contentType will have the following values removed: GenericTemplate, ListTemplate, Postback, & Reactions. Within MessageContent, the following properties will be removed: generic, list, reactions, mention, postback.
Within the ContentQuickReply contract, the id field will be removed.
Within the ContentButtonResponse contract, the id field will be removed.
Change Category
API
Change Context
The post text API is currently using a set of models that was initially designed to fit a hybrid deployment model for PureEngage and PureConnect. Afterwards, another set was added for support within GenesysCloud conversations. The API was always intended to be used by GenesysCloud only.
Change Impact
The backend service up until this time has only used the following properties within MessageContent for requests and responses: contentType, quickReply, buttonResponse, card, carousel, & generic. With these changes, the id fields for both quickReply and buttonResponse have been ignored. The ContentGeneric contract has been deprecated in favor of the ContentCard contract.
Date of Change
No sooner than 04 January, 2023
Impacted APIs
POST /api/v2/textbots/bots/execute
References
[CW-2893]