Service API v2.2.1
Added security feature that blocks users from accessing media files which do not belong to them.
Changes that added functionality
View All TagsAdded security feature that blocks users from accessing media files which do not belong to them.
Added security feature that blocks users from accessing media files which do not belong to them.
Added security feature that blocks users from accessing media files which do not belong to them.
Added support for the new Service API feature (v2.2) to receive custom Agent attributes.
When doing the GET /messages call, you'll now receive the custom Agent attributes.
content type of the /services call was image/png and it
should've been application/jsonX-XSS-Protection: 1; mode=block Enables XSS filtering. Rather than sanitizing the page, the browser will prevent rendering of the page if an attack is detected.X-Content-Type-Options: nosniff Prevents MIME-sniffingX-Frame-Options: SAMEORIGIN The page can only be displayed in a frame on the same origin as the page itselfdemo value which, if true, will make sure this account is correctly configured for use in the mobile Parley Demo app (android/ios)GET /accounts/users endpoint, we would only return 10 users. Now we return all of the users.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
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.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