Client API v1.6.14
Fixed an issue where the GET /messages call would fail if a message could not be processed correctly
Fixed an issue where the GET /messages call would fail if a message could not be processed correctly
Small improvements to how we deal with media uploads
Small improvements to how we deal with media uploads
Small improvements to how we deal with media uploads
Added message statuses. Message now have a status property which can be one of the following values
2 This means the message has been received by the Parley API. This is the default status when the message has been
sent using the API.3 This means that the message has been received by the client but not read/rendered yet.4 This means that the message has been read/rendered by the clientAdded support for Services that do not wish to receive any callbacks on new messages. These type of Services are used only for accessing the Service API.
Added support for Services that do not wish to receive any callbacks on new messages. These type of Services are used only for accessing the Service API.
Added support for Services that do not wish to receive any callbacks on new messages. These type of Services are used only for accessing the Service API.
The previous release fixed an issue where the changeOwner event didn't include the newOwner property. This release
fixes another potential scenario where this could happen.
Fixed an issue where we send out a changeOwner event, to the services, when the ownership did not actually change.
This event also didn't include the newOwner property.