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 clientThe status will only be updated if you use a web client that has support for this. It should call the
PUT /messages/status/:newStatus endpoint with the new status.
You can update the status of a message with the new endpoint PUT /messages/status/:newStatus. For more info
see PutMessagesStatus
You can retrieve a list of messages which are "unseen" (/unread) using the new endpoint GET /messages/unseen/count.
For more info
see GetMessagesUnseen
changeOwner event didn't include the newOwner property. This release
fixes another potential scenario where this could happen.]]>changeOwner event, to the services, when the ownership did not actually change.
This event also didn't include the newOwner property.]]>[Goolge](https://google.com) and [Bing](https://bing.com) are both search engines
") was used, on the same line, before
the url;
This is a url to the "Google" search engine [Goolge](https://google.com)
This is now fixed so the url should correctly render
]]>Firebase Cloud Messaging V1 (push type 6) replaced APNS in 2019. This means that the following endpoints will not accept APNS anymore:
POST /push/test/:platformPUT /push/:platformGET /push/:platform2).Firebase Cloud Messaging V1 (push type 6) replaced APNS in 2019. There are no endpoints in this API that directly deal
with APNS but, APNS used to be called when you send a message or did another action that would trigger a push notification.