Simulate a customer scanning (staging only)
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.
/{locale}/shop/qr-card/{sessionId}/simulate-scanResolves 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.
Authorization
apiKey apiSecret Partner API key from the Partners Portal. Always sent together with X-API-Secret.
In: header
Partner API secret. Always sent together with X-API-Key.
In: header
Path Parameters
Locale code
Value in
- "lt"
- "en"
From qr-card/generate
Request Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
Response Body
application/json
curl -X POST "https://example.com/lt/shop/qr-card/550e8400-e29b-41d4-a716-446655440000/simulate-scan" \ -H "Content-Type: application/json" \ -d '{ "loyalty_card_id": 43 }'{ "success": true, "code": 200, "request_id": "550e8400-e29b-41d4-a716-446655440000", "message": "Success message", "data": {}}Poll QR Card Session Status GET
Poll the status of a QR card scan session (fallback if the socket is unavailable)
Realtime Connection Config GET
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`.