33 posts tagged with "Service API"

Changed media ID to a UUID. This way it is easier to deal with image paths. This is also some pre-work for the future where we want to use UUID's for all our image endpoints.

• Added a new API endpoint to remove the "current" Agent from a conversation.
• The GET /messages endpoint will return null for the (root) agent key denoting that no agent is currently actively handling this conversation.

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 security feature that blocks users from accessing media files which do not belong to them.

• Added a new feature for setting custom agent properties. You can now pass in any custom property you want for an Agent and it will be saved in the Parley system.
• Fixed an issue in the API documentation where the content type of the /services call was image/png and it should've been application/json

Fixed an issue where new messages would not be sent to the Service when the Service is disabled (due to multiple failed attempts to communicate with the Service).
When the Service is disabled it only means that enqueued messages won't be tried anymore. All new messages are still tried 1 time before they enter the Queue.

More info about the Queuing mechanism

Fixed issue where messages, that should be send to other Services, were not send via our asynchronous Queue.
Which means that if the receiving Service is "slow", your api call would be slow aswell.

Example:
POST /users/{userId}/messages sends a message to the Client and connected Services.
If the connected Service is slow and responds after 1 second, your POST /users/{userId}/messages call would take ~ 1 second.

Now it doesn't matter if the connected Service is slow, because POST /users/{userId}/messages will put the message into a Queue which sends the message asynchronous to the connected Service. Resulting in your api call only taking a couple ms.

More info about the Queuing mechanism

Fixed issue where if we needed to Push something to the Clients, we would put those messages into a queue but they wouldn't get picked up directly.
Now when something enters the queue it gets picked up immediately.

This should increase performance on the sending of push notifications to clients.

Fixed issue where if we needed to Push something to the Clients, we would put those messages into a queue but they wouldn't get picked up directly.
Now when something enters the queue it gets picked up immediately.

This should increase performance on the sending of push notifications to clients.