Loyalty.lt
Realtime

Realtime Connection Config

Connection details for the realtime channel, which speaks the Pusher protocol. 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`.

GET/{locale}/shop/realtime/config

Connection details for the realtime channel, which speaks the Pusher protocol. 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

apiKey apiSecret
X-API-Key<token>

Partner API key from the Partners Portal. Always sent together with X-API-Secret.

In: header

X-API-Secret<token>

Partner API secret. Always sent together with X-API-Key.

In: header

Path Parameters

locale*string

Locale code (lt, en)

Value in

  • "lt"
  • "en"

Header Parameters

X-API-Key*string

API Key

X-API-Secret*string

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"  }}

Simulate a customer scanning (staging only) POST

Resolves an open QR card session as if the customer had scanned it, so a QR integration can be tested without a phone. Broadcasts the same card_identified and status_update frames a real scan does. Refused on production.

List Shops GET

Get a paginated list of shops