How to create health ID with aadhar otp

#1

We have integrated /v1/registration/aadhaar/createHealthIdWithAadhaarOtp to create health ID with aadhar otp but the following API has been removed from version1.Can anyone provide the updated sequence of API’s and the parameters to be generated to create health id with aadhar otp in version 2 .

#2

AFAIK:

  1. /v2/registration/aadhaar/generateOtp
  2. /v2/registration/aadhaar/verifyOTP
  3. /v2/registration/aadhaar/phr-address
  4. /v2/registration/aadhaar/confirm
#3
  1. /v2/registration/aadhaar/confirm it says verify mobile number error at 4th point but my same mobile number is linked with aadhar
    Screenshot (35)
    Screenshot (35)1280×1024 87.9 KB
#4

AFAIK:

  1. /v2/registration/aadhaar/generateOtp
  2. /v2/registration/aadhaar/verifyOTP
  3. /v2/registration/aadhaar/checkAndGenerateMobileOTP
  4. /v2/registration/aadhaar/verifyMobileOTP (If point 3 returns mobileLinked: false)
  5. /v2/registration/aadhaar/phr-address
  6. /v2/registration/aadhaar/confirm
#5

Sorry I have updated my answer. I think we need to call checkAndGenerateMobileOTP ( 1. /v2/registration/aadhaar/checkAndGenerateMobileOTP). If it returns mobileLinked: false then we need to do mobile verification.

Not sure though.

#6

Hey

We are on the same boat, struggling to understand the flow. Does anyone has information on what’s the right sequence of API calls?

#7

I have used the below sequence of api’s

  1. /v2/registration/aadhaar/generateOtp
  2. /v2/registration/aadhaar/verifyOTP
  3. /v2/registration/aadhaar/checkAndGenerateMobileOTP
  4. /v2/registration/aadhaar/verifyMobileOTP
  5. /v2/registration/aadhaar/confirm

In the following sequence provided to create health id using aadhar /v2/registration/aadhaar/verifyMobileOTP gives incorrect otp error even after providing correct otp.

Screenshot (33)
Screenshot (33)1280×1024 77.7 KB
Screenshot (34)
Screenshot (34)1280×1024 86.6 KB

#8

For us, step 5 is always giving out errors. 401 Unauthorized. Whereas other APIs work and other registrations are happening fine. We are passing the Authorization header that is required as per ther swagger.

Tried to execute on swagger too after adding the required headers but it only fails at the same last step.

{
    "timestamp": "2022-01-27T05:38:58.194+0000",
    "status": 401,
    "error": "Unauthorized",
    "message": "Unauthorized",
    "path": "/api/v2/registration/aadhaar/confirm"
}
#9

@ayush please use /v2/account/phr-linked

use the mentioned API to link the ABHA address to ABHA Number.

request:
{
“phrAddress”: “xxx@sbx”,
“preferred”: true
}

Please call confirm api after this.