Fetch a fresh QR/code
On demand; the workers also refresh it on a timer and push it through SSE. With ?method=qr, takes over a pairing the dependent was doing by code on their own phone (the fallback "Vocês estão juntos agora?"): same session, a QR on this screen, the code stops working. Owner only.
BearerAuthorizationBearer <JWT>uid*stringseat uid
uuidmethod?"qr"qr: take the challenge over to this screen — the fallback "Vocês estão juntos agora?" while the dependent was being shown a code. Same session, the code stops working
"qr"The pairing with its current challenge (null when the provider has none yet)
application/json- response
success*truetruedata*curl -X POST 'http://localhost:3000/seats/497f6eca-6276-4993-bfeb-53cbbbba6f08/pairing/challenge'{ "success": true, "data": { "uid": "string", "channel": "whatsapp", "status": "starting", "method": "qr", "challenge": { "kind": "qr", "image": "string", "mime": "string", "expiresAt": "2019-08-24T14:15:22Z" }, "challengeShownTo": "guardian", "identity": { "phone": "string", "pushName": "string", "avatarUrl": "string" }, "reconnectAttempts": 0, "nextRetryAt": "2019-08-24T14:15:22Z", "failureReason": "string", "pairedAt": "2019-08-24T14:15:22Z", "lastSeenAt": "2019-08-24T14:15:22Z", "endedAt": "2019-08-24T14:15:22Z", "createdAt": "2019-08-24T14:15:22Z" }}Unlink DELETE
Logs the provider session out and forgets it. Owner only. 204 even with nothing open.
The dependent's profile picture GET
The bytes of the dependent's own WhatsApp profile picture, copied into our storage when the pairing connected. Served here because the provider's own link is on WhatsApp's CDN: it expires and is not the browser's to follow. 404 whenever there is none — many people hide their picture, and the screen falls back to initials. Never a contact's picture: those people never consented.