Websocket client notifications

General information

All communication on websockets is done with STOMP protocol. In all cases client application needs to establish websocket/stomp connection on url: {ORDERING_STACK_API_URL}/ws using connection header login containing valid access token (the same which is used for accessing Ordering Stack API, can be aquired with /auth-oauth2/oauth/token endpoint).

Order notifications

Client application can subscribe to: /order-changes/{user-uuid}/{order-uuid}.

For this subscription client will receive messages regarding order (specified with order-uuid). Subscribing users can be order creator or other user who aquired access to this order.

Notification about orders from venue

Client application can subscribe to: /kds/{tenantId}/{venueId}.

For this subscription client will receive messages regarding completed but not closed orders for this venue. Notification will arrive when new completed order will appear, when this order is modified (status, other changes) and when is closed.

User notifications

Client application can subscribe to: /kds/{tenantId}/{user-uuid}.

All messages reveived with this subscription are user specific (user_uuid is received from /auth-oauth2/oauth/token). For this subscription client will receive messages regarding user activity. It can be errors (for example user sent command to add product to the basket that can not be added), basket updates, upsells and other messages.

Notifications for venue settings changes

Client application can subscribe to: /venue/{tenantId}/{venueId}.

Client will receive messages when venue configuration changes including venue device changes.


Example with source code

Example usage of websocket notifications can be found in example POS integrator application: https://github.com/orderingstack/pos-integrator-example .