Real-time QR code challenge management via WebSocket connections
Region | API URL |
---|---|
US (Oregon) | wss://api-ws.authsignal.com/ws-v1-challenge |
AU (Sydney) | wss://au.api-ws.authsignal.com/ws-v1-challenge |
EU (Dublin) | wss://eu.api-ws.authsignal.com/ws-v1-challenge |
Sec-WebSocket-Protocol
header:
authsignal-ws
- identifies the Authsignal WebSocket sub-protocol.x.authsignal.tenant.<your-tenant-id>
- use when the challenge is anonymous (user is not known yet).x.authsignal.token.<token-from-track>
- use when the challenge is for a known user; supply the token returned by the track request.CREATE_CHALLENGE
message to initiate a challengeCHALLENGE_CREATED
confirmationSTATE_CHANGE
messages as the challenge progresses through statesunclaimed
- Challenge created but not yet claimed by a user (This state will not be included in the state change messages)claimed
- User has claimed the challenge on their deviceapproved
- User has approved the challengerejected
- User has rejected the challenge