Attendant - SocketIO
The Attendant API publishes async events to the SocketIO service for edge applications to consume.
What is SocketIO and how it works?
Topics that Attendant API expose
att.private.notification.assistance-requests.v1
- assistance request is created or updatedatt.private.notification.assistance-request-processed.v1
- assistance request is processed (/act) endpoint is called on assist reqatt.private.notification.assistance-request-deleted.v1
- assistance request is deletedatt.private.notification.baskets.v1
- basket is created or updatedatt.private.notification.basket-deleted.v1
- basket is deletedatt.private.notification.workstations.v1
- workstation is created or updatedatt.private.notification.workstation-deleted.v1
- workstation is deleted
Note: no message will be published if entity is expired (no updates for 10 days) and is removed from the database.
Full AsyncAPI schema for specified topics can be found here
Note: Please keep in mind that attributes in a schema specified using
This-Case
, but SocketIO will turn any attribute tothisCase
.
How it works?
For each data mutation for Workstation, Basket or Assistance Request, Attendant API will publish a message to the SocketIO service. Edge application may choose to sub to it to get real-time updates for entities. In attempt to save traffic, we do not include all the data when entity is updated, but only identifiers and fields that changes. Please go through the schema to see what fields are mandatory (marked as required) and what are optional and can be omitted.