Tuvali API Documentation
Firstly, for establishing the secured connection over BLE the connection params which include name
and key
needs to be exchanged between the two devices. This exchange of parameters can be accomplished but is not limited to by using a QR code.
For example, use a QR code generator to visually display params and a QR code scanner to get params. A mobile app that displays a QR code can act as an Verifier
by including its connection params as data in the QR code and another device can act as Wallet
which scans the QR code, it can extract the connection parameters and initiate a BLE connection with the advertising device.
Connection parameters exchange
The device on which the QR code is displayed shall generate connection parameters using the
startAdvertisement()
method:
The device that scans the QR code will extract the connection parameters from the QR code and set its connection parameters using the
startAdvertisement()
method :
The connection param is a URI with a name & a key. The name
is the client's name & the key
is the verfier's public key.
The
key
part of the data is the same data that will be advertised by theverifier
device but in hex-encoded form.
E.g: OVPMOSIP://connect:?name=<>&key=<verifier public key>
Establishing connection
The device that displays the QR code will become Verifier
and the other device that scans the QR code will become discoverer
and will attempt to discover the devices based on the pre-exchanged uri
.
Share data
Once the connection is established, wallet app can send the data
and verifier app can acknowledge it.
The following sequence of actions should be performed to transfer data over BLE:
Verifier must start advertising by calling
verifier.startAdvertisement(name)
methodSubscribe to events using
wallet.handleDataEvents
Initiate the secure connection using
wallet.startConnection(uri)
. The Wallet public keys are exchanged with verifier on successful connection.Wallet calls
wallet.sendData(payload)
to transfer requisite data over BLE.Send VC response - Verifier can exchange "Accept/Reject" status to Wallet with the following message type for
verifier.sendVerificationStatus
method
Subscribe to events
Data received from other apps via BLE can be subscribed to using: Tuvali sends multiple events to propagate connection status, received data etc. These events can be subscribed to by calling:
on Wallet:
on Verifier:
Here are the different types of events that can be received
Common Events
Events which are emitted by both Wallet and Verifier
onConnected
{"type": "onConnected"}
on BLE connection getting established between Wallet and Verifier
onSecureChannelEstablished
{"type": "onSecureChannelEstablished"}
on completion of key exchange between Wallet and Verifier
onError
{"type": "onError", "message": "Something Went wrong in BLE", "code": "TVW_CON_001"}
on any error in Wallet or Verifier
onDisconnected
{"type": "onDisconnected"}
on BLE disconnection between Wallet and Verifier
Wallet Specific Events
onDataSent
{"type": "onDataSent"}
on completion of Data transfer from the Wallet Side
onVerificationStatusReceived
{"type": "onVerificationStatusReceived", "status": "ACCEPTED"}
on received verification status from Verifier
Verifier Specific Events
onDataReceived
{"type": "onDataReceived"}
on receiving data from the Wallet Side
Connection closure
The device on which app is running can destroy the connection by calling disconnect() method:
Tuvali & Inji Integration
Last updated