Call back not received for v3

#1

@IntegrationSupport
i have used the below curl and receiving the response as 202 but no callback is receieved

curl --location ‘https://dev.abdm.gov.in/hiecm/api/v3/token/generate-token’
–header ‘REQUEST-ID: 55bdc229-c5c9-4ee5-a9b6-410b4f4c6564’
–header ‘X-HIP-ID: HIP_0012345’
–header ‘TIMESTAMP: 2023-10-04T09:30:41.473Z’
–header ‘X-CM-ID: sbx’
–header ‘Authorization: Bearer eyJhbGciOiJSUzI1NiIsInR5cCIgOiAiSldUIiwia2lkIiA6ICJBbFJiNVdDbThUbTlFSl9JZk85ejA2ajlvQ3Y1MXBLS0ZrbkdiX1RCdkswIn0.eyJleHAiOjE2OTY0MzE5NjYsImlhdCI6MTY5NjQxMDM2NiwianRpIjoiN2ZjOTg4OTYtMjM3NC00Mzg3LWJhMTMtOGE5ZjQ1YmNiYWRhIiwiaXNzIjoiaHR0cHM6Ly9kZXYubmRobS5nb3YuaW4vYXV0aC9yZWFsbXMvY2VudHJhbC1yZWdpc3RyeSIsImF1ZCI6ImFjY291bnQiLCJzdWIiOiIwODI2ODkyNy1kMDUxLTQ3ZGUtYTE3Mi0yYWRjYmJlOWVlYTYiLCJ0eXAiOiJCZWFyZXIiLCJhenAiOiJTQlhfMDAyOTI4Iiwic2Vzc2lvbl9zdGF0ZSI6IjFiMDliNjI3LWY0NWMtNDhkMi05MTg3LTkzZjJmY2Q1NDc1YSIsImFjciI6IjEiLCJhbGxvd2VkLW9yaWdpbnMiOlsiaHR0cDovL2xvY2FsaG9zdDo5MDA3Il0sInJlYWxtX2FjY2VzcyI6eyJyb2xlcyI6WyJoZnIiLCJoaXUiLCJvZmZsaW5lX2FjY2VzcyIsImhlYWx0aElkIiwicGhyIiwiT0lEQyIsImhlYWx0aF9sb2NrZXIiLCJoaXAiLCJocF9pZCJdfSwicmVzb3VyY2VfYWNjZXNzIjp7IlNCWF8wMDI5MjgiOnsicm9sZXMiOlsidW1hX3Byb3RlY3Rpb24iXX0sImFjY291bnQiOnsicm9sZXMiOlsibWFuYWdlLWFjY291bnQiLCJtYW5hZ2UtYWNjb3VudC1saW5rcyIsInZpZXctcHJvZmlsZSJdfX0sInNjb3BlIjoib3BlbmlkIGVtYWlsIHByb2ZpbGUiLCJjbGllbnRIb3N0IjoiMTAuMjMzLjY5Ljc2IiwiY2xpZW50SWQiOiJTQlhfMDAyOTI4IiwiZW1haWxfdmVyaWZpZWQiOmZhbHNlLCJwcmVmZXJyZWRfdXNlcm5hbWUiOiJzZXJ2aWNlLWFjY291bnQtc2J4XzAwMjkyOCIsImNsaWVudEFkZHJlc3MiOiIxMC4yMzMuNjkuNzYifQ.dFTSPEpmQGBs3l-2sLGDqW9ex_ISG_WVHQ5U8KAtD8M3mBLf_E-4IJ6SV864EJYwe88DwuhB86510HMIzWqSwhIQzGcHSFwEvh7y9axes_bQo-SRsuifIDbcgvGG_7POnWU-DL0Xuw98qR4t_uXU2jHvzEhsheuwOwxqETtO7B4aP3VEPVwuvYyiQSwta4GaLQ8orqJ3cJwbWUNdUzTKNydsgAG8IwBHyYNi3BCfysiAY4ipRkcpNHJ8hrn54qRk2nIdjIKgOT7dvu1riemRjSD9wFVBb9pkItvqnVv4RE0Iy0BqazNB9F1VJzExDjN_tKuMAmJBy5MxXWdIBQbzVg’
–header ‘Content-Type: application/json’
–data-raw '{
“abhaNumber”:“91263315824866”,
“abhaAddress”:“priyavelu@sbx”,
“name”:“Velu Karthick M”,
“gender”:“M”,
“yearOfBirth”:“2001”
}
’
https://api.plenome.com/abha-callback this is the registered callback url
how should it be resolved

1 Like
#2

@raunaqpradhan Kindly assist on this trial.

#3

@raunaqpradhan kindly help me to solve the issue which i mentioned above

#4

@IntegrationSupport still i am facing the same issue ,is there any update

#5

@pranab @raunaqpradhan Kindly assist on the above V3 issue

#6

@pranab @raunaqpradhan kindly help me to resolve the issue as i cant proceed without it

#7

@velu You can also use v1 api for M1 integration as v3 is not a mandate. If you are in urgency please use v1 api’s. postman collection available over sandbox website

#8

@IntegrationSupport
can you give me the v1 api url please as i am confused

#9

@velu Sharing with you all the documentation links for M1

https://app.swaggerhub.com/apis-docs/abdm.abha/abha-service/1.0
In this swagger link at the top you will find the base url.

Sharing postman collection also:
https://sandbox.abdm.gov.in/docs/postman_collections

https://sandbox.abdm.gov.in/abdm-docs/CreateOfAbhaNumber (You can also check new documentation).

#10

@IntegrationSupport
do we have v3 support for ABHA APP on SBX or not ??
i need to check the use case of patient scanning the HIP QR CODE
but when i use ABHA APP i got callback on

v1.0/patients/profile/share

rather i was expecting on

api/v3/hip/patient/profile/share

if abha app doesn’t have v3 support …then from where we can check this use case
also
let’s say if we developed this v3 flow both for call and callback
but again the ABHA APP Is on V1 then
do we have manage both in our system???

1 Like
#11

@IntegrationSupport …need support here pls

#12

@deeptomar93 There is no relation of V3 with ABHA app. V3 is the version for the api you use. For Scan and share please check this link - https://sandbox.abdm.gov.in/abdm-docs/ABDM_M3_V1
Check Api mapping document

#13
/v1/patients/profile/share App Active /hiecm/api/v3/profile/on-share
/v1.0/patients/profile/on-share Gateway Active {callback_url}/v3/hip/profile/share
/v1.0/patients/profile/share Gateway Active {callback_url}/v3/app/profile/on-share

these are the APIS
now ,when i scanned the HIP QR Code from ABHA SBX APP i get callback on v1.0/… /profile/on-share

@IntegrationSupport
okay
which means the app must have called the API for v1.0/patients/profile/share only not the latest v3/profile/share

right???

so is the ABHA APP IS GOING TO CALL v1 api only or v3 in future

1 Like