Search via mobile number not returning abha details

Health ID
#1

Hi @IntegrationSupport,

I am creating a PHR address using MOBILE NUMBER flow with the following endpoint
POST https://phrsbx.abdm.gov.in/api/v1/phr/registration/create/phr endpoint with the following payload

Body
{
“alreadyExistedPHR”: “false”,
“phrAddress”: “kavitha198807”,
“transactionId”: “8e0ff19d-895e-49d9-a22f-22f4b18551e4”
}

and get a success response, indicating creation of ABHA address.

{
“token”: “eyJhbGciOiJSUzUxMiJ9…”,
“expiresIn”: 7200,
“refreshToken”: “eyJhbGciOiJSUzUxMiJ9…”,
“refreshExpiresIn”: 432000,
“phrAdress”: “kavitha198807@sbx”,
“authTs”: “wD2Bz9kM/7LMh/mthplpu83eRoSq3qQij3CL9RFgF5Q=”
}

When I search using the mobile number used to create the above ABHA address using the below endpoint:

POST https://healthidsbx.abdm.gov.in/api/v1/search/searchByMobile

Body
{
“mobile”:“9XXXXXXX98” //NUMBER IS MASKED
“name”: “kavitha anand b l”,
“gender”: “F”,
“yearOfBirth”: “1988”
}

It returns an empty response indicating ABHA was not found. Is this expected behavior? additional info which might be useful, I have created the ABHA address using mobile flow, but it is not linked to ABHA number.

please clarify,

Thanks.

#2

@IntegrationSupport can you please help with this?

#3

@Vjdev Please guide in this trail.

#4

@RohanChristopher707 - Abha address , kavitha198807@sbx is not linked. We checked at our end, API is working fine. Please see the curl below.

curl --location ‘https://healthidsbx.abdm.gov.in/api/v1/search/searchByMobile’
–header ‘accept: /’
–header ‘Accept-Language: en-US’
–header ‘Content-Type: application/json’
–header ‘Authorization: Bearer eyJhbGciOiJSUzI1NiIsInR5cCIgOiAiSldUIiwia2lkIiA6ICJBbFJiNVdDbThUbTlFSl9JZk85ejA2ajlvQ3Y1MXBLS0ZrbkdiX1RCdkswIn0.eyJleHAiOjE3MDgwNjQ3MTUsImlhdCI6MTcwODA2MzUxNSwianRpIjoiOTMyYjEwZDItNDBiZC00MzJiLThmZDgtMzdlNGViYWI0NTBhIiwiaXNzIjoiaHR0cHM6Ly9kZXYubmRobS5nb3YuaW4vYXV0aC9yZWFsbXMvY2VudHJhbC1yZWdpc3RyeSIsImF1ZCI6ImFjY291bnQiLCJzdWIiOiJhY2UyMTYzMi00NmFmLTQyZmItYjg1Yi1lZDYyYjliMjU2ZDMiLCJ0eXAiOiJCZWFyZXIiLCJhenAiOiJZRVBfVEVTVCIsInNlc3Npb25fc3RhdGUiOiIwZjFiZDQwNy04ZjgwLTRkYzktOGE2OC00OTQ2ZjNjNjcwMzUiLCJhY3IiOiIxIiwiYWxsb3dlZC1vcmlnaW5zIjpbImh0dHA6Ly9sb2NhbGhvc3Q6OTAwNyJdLCJyZWFsbV9hY2Nlc3MiOnsicm9sZXMiOlsiSGlkSW50ZWdyYXRlZFByb2dyYW0iLCJoZnIiLCJoaXUiLCJvZmZsaW5lX2FjY2VzcyIsIkhpZF9DaGlsZCIsImhlYWx0aElkIiwicGhyIiwiT0lEQyIsImhlYWx0aF9sb2NrZXIiLCJoaXAiLCJocF9pZCJdfSwicmVzb3VyY2VfYWNjZXNzIjp7IllFUF9URVNUIjp7InJvbGVzIjpbInVtYV9wcm90ZWN0aW9uIl19LCJhY2NvdW50Ijp7InJvbGVzIjpbIm1hbmFnZS1hY2NvdW50IiwibWFuYWdlLWFjY291bnQtbGlua3MiLCJ2aWV3LXByb2ZpbGUiXX19LCJzY29wZSI6Im9wZW5pZCBlbWFpbCBwcm9maWxlIiwiY2xpZW50SWQiOiJZRVBfVEVTVCIsImVtYWlsX3ZlcmlmaWVkIjpmYWxzZSwiY2xpZW50SG9zdCI6IjEwLjIzMy43Mi4yNDUiLCJwcmVmZXJyZWRfdXNlcm5hbWUiOiJzZXJ2aWNlLWFjY291bnQteWVwX3Rlc3QiLCJjbGllbnRBZGRyZXNzIjoiMTAuMjMzLjcyLjI0NSJ9.mX1lIcE7jo4VB4-e9Yivoj8fLlgMtYO2UUrU7YYJKvgDGn8XDaS71vexOX3qfK_mYBk1TCxwEE0BJF6yl2b7fBPBwyEGaufk5mvIf89RaSVGTTGU2G1YWixGVDv5NmqFKXfmjxkoVvsfwLAvglDkzNI9I0BSnyYsOaVmMh3PYlE8rfEBOeuUufWE2ONck5cSAbFi6f720kVpw4N6FNYxhU0_XXONQF8q8BPg5EQYozoqU0PgE8yu9XrrjDBZCwVzvcghaYjSJV4OeKnlFgpJQ3PRNQbJMXoEFjJwz1el2c5nqdRg2J0lB99Nxo195patUftvzNRf4ZsGaLo2rpmt4g’
–data ‘{
“gender”: “x”,
“mobile”: “63xxxxxxxx”,
“name”: “vxxxx xxxx”,
“yearOfBirth”: “2xxx”
}’

#5

@IntegrationSupport this user does not have a healthId number hence, the phr address kavitha198807@sbx is not linked, this is for a scenario, where a user is reluctant to share aadhaar number, hence we use the mobile number and generate a phr address for the user, how do we link this phr address in this case? CC @Vjdev