Pair Device

The ID Wallet app allows you to issue digital identities and credentials on the mobile devices of your users (employees, contractors, or admins) that are used for multi-factor authentication, passwordless authentication, and verification. Below is a workflow of the ID Wallet app.

All APIs are protected using OAuth2 Access Token. Pairing the ID Wallet app with the organization initiates the user authentication process to acquire JSON Web Token (JWT) based Access token consisting of user claims and scopes to access protected resources.

The Authorization Header with the access token in an HTTP Request is usually, but not always, sent along with the requests to access a resource. In the documented API, it is mentioned for each API described if an access token is required or not to access a protected resource.

The latest TLS Protocol is recommended to securely transmit the data.

This API endpoint pairs the user's device with the organization.


Headers

  • Authentication: Bearer <JWT>
  • Accept: application/json
  • Content-Type: application/json

Path Parameters

ParametersTypeDescription
organizationNamestringDenotes the name of the organization.

Body Parameters

ParametersTypeDescription
requestUserDeviceobjectThe object that contains the body for the API call.

requestUserDevice Object

ParametersTypeDescription
appNamestringThe name of the app (ID Wallet).
appRegIDintegerThe registered ID of the app (ID Wallet).
appVersionintegerThe version of the app (ID Wallet).
deviceManufacturerNamestringThe name of the device manufacturer.
deviceModelNamestringThe model name of the device.
devicePublicKeyAlgorithmstringThe public key algorithm of the device. This key would be used to encrypt the token and share across the user device.
devicePublicKeyB64stringThe device public key in base 64 format.
friendlyNamestringThe friendly name given to the device.
gpsCoordinatesstringThe GPS coordinates (location) of the user device from where the device was used. The location coordinates are returned only if the permission to access the location is allowed by the user while launching the app on the mobile device else it will return 0.0,0.0.
operatingSystemstringThe operating system of the device. E.g.: Android/iOS
organizationNamestringThe name of the organization.
osApiVersionstringThe API version of the operating system. This field is specific for Android devices only. E.g.: API level 31
osVersionstringThe version of the operating system (E.g.: Android 12.0/iOS 15.0)
TypestringThe type of the mobile device-Mobile/iPad/Note/Tablet.
uniqueIdentifierintegerThe unique ID number of the device.
uuidintegerThe secret key generated for pairing the device. Expires after 30 seconds.

Response Object

ParameterTypeDescription
idNumberThe ID associated with the user.
nameStringThe username of the user.
fullNameStringThe full name of the user.
organisationNameStringThe name of the organization to which the user belongs.
organisationIdNumberThe ID of the organization to which the user belongs.
groupIdStringThe ID of the group to which the user belongs.
groupNameStringThe name of the group to which the user belongs.
statusStringThe status of the user, indicating whether they are ready for reissuance or not.
firstNameStringThe first name of the user.
lastNameStringThe last name of the user.
emailStringThe email address of the user.
userPrincipalNameStringThe principal name of the user.
enrollmentStatusStringThe enrollment status of the user.
userStatusStringThe status of the user.
canIssueIdentityBooleanIndicates whether the user can issue an identity.
createdDateDateThe date and time when the user was created.
lastModifiedDateDateThe date and time when the user was last modified.
userBiometricsArrayAn array containing details of the user's biometrics, such as type, format, and image data.
wfMobileIDStepDetailsObjectAn object containing details of the mobile ID step, including configuration for onboarding, face verification, adjudication, and hardware-backed authentication.
Language
URL