Web library v1.4.1
Fixed an issue where images (that the client sent) weren't visible. They should now render correctly.
Fixed an issue where images (that the client sent) weren't visible. They should now render correctly.
Fixed an issue where if a Client sends an Image, the Service would receive "📸" instead of the path to the Image. This also caused the web-library to fail when trying to show this Image.
There is a bug in this version which prevents showing images. They are still sent to the Service but the Client cannot see them.
This is fixed in v1.4.1
Added
Fixed
00:00Added
Fixed issue that caused the Webhook push notification's message field to be empty in some cases
userAdditionalInformation if you have different chats on different pages on your website./devices call was hardcoded on version 1.2 of the Client API. This is the call made when you have push enabled and the client accepts browser notifications to register a pushToken with your device so you can receive push notifications."you" as the Agent in the conversation export. It now shows "Operator" if the Agent name is not available.default property was always false in the GET /services endpointchangedOwner webhook was not send through the Service Queue. Which meant that your PUT /users/{userId}/owner could take very long to complete if the connected Services were slow to respond.Added support for multiple Services, which means you can have more than 1 Service connected to your Account. All messages that you send using the Client API are being send to all connected Services. On the Service side you will need to use Service aPI v2.1.0.
Added accountIdentification to the webhook messages so you can easily see from which Account the message is originated. Previously we only sent the accountId which is used internally.
Added a Service Queue, which Queues all messages that are send from the Client to the Service. If you are a Service administrator, please take a look at: https://developers.parley.nu/docs/service-queue
Added the possibility to send "rich" messages, but for this to be used on the Client side we are waiting on the next release for the Client API.
So Clients can not yet receive these rich messages. However, you can still use this endpoint to send normal messages/images.
More info: https://api.parley.nu/serviceApi/v2.1/doc/#operation/PostMessages
Added various Security headers to our responses
Fixed issue where the "fullscreen" mode, on mobile iOS devices using Safari, was not correctly updating it's height.
There are some devices which are unsupported, here is the list:
Basically, if your device is up-to-date you shouldn't have any problems.