Realtime Connection Config
Laravel Reverb (Pusher protocol) connection details for storefront realtime. The QR channels are public — the unguessable session id in the channel name is the secret — so no per-session token is issued. Subscribe to `qr-login.{session_id}` or `qr-card.{session_id}` and bind `status_update`.
/{locale}/shop/realtime/configLaravel Reverb (Pusher protocol) connection details for storefront realtime. The QR channels are public — the unguessable session id in the channel name is the secret — so no per-session token is issued. Subscribe to qr-login.{session_id} or qr-card.{session_id} and bind status_update.
Authorization
bearerAuth Enter JWT token in the format: Bearer {token}
In: header
Path Parameters
Locale code (lt, en)
Value in
- "lt"
- "en"
Header Parameters
API Key
API Secret
Response Body
application/json
curl -X GET "https://example.com/lt/shop/realtime/config" \ -H "X-API-Key: lty_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" \ -H "X-API-Secret: your_api_secret_here"{ "success": true, "message": "Realtime configuration", "data": { "key": "968c26be26b3d344e689e3319d1aa50d", "host": "ws.loyalty.lt", "port": 443, "scheme": "https", "channel_prefix": { "qr_login": "qr-login.", "qr_card": "qr-card." }, "event": "status_update" }}Health Check GET
Check if the Shop API is running and all services are operational
Publish to an Upload Session Channel POST
Broadcast to the public `upload-session.{session_code}` channel. Used by storefront integrations that hand a file from a phone to a desktop, because Reverb has no client-side publish. Call this from your server — it requires the API secret — never from a browser.